Downloads of v 3.0.20171219.105559:


Last Update:

02 Jun 2019

Package Maintainer(s):

Software Author(s):

  • JetBrains


dotmemory unit testing jetbrains

dotMemory Unit Standalone Launcher (Portable)

  • 1
  • 2
  • 3

3.0.20171219.105559 | Updated: 02 Jun 2019



Downloads of v 3.0.20171219.105559:



Software Author(s):

  • JetBrains

  • 1
  • 2
  • 3
dotMemory Unit Standalone Launcher (Portable) 3.0.20171219.105559

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install dotMemory Unit Standalone Launcher (Portable), run the following command from the command line or from PowerShell:


To upgrade dotMemory Unit Standalone Launcher (Portable), run the following command from the command line or from PowerShell:


To uninstall dotMemory Unit Standalone Launcher (Portable), run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade dotmemory-unit.portable -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade dotmemory-unit.portable -y --source="'INTERNAL REPO URL'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install dotmemory-unit.portable
    name: dotmemory-unit.portable
    version: '3.0.20171219.105559'
    state: present

See docs at

chocolatey_package 'dotmemory-unit.portable' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '3.0.20171219.105559'

See docs at

cChocoPackageInstaller dotmemory-unit.portable
    Name     = "dotmemory-unit.portable"
    Version  = "3.0.20171219.105559"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'dotmemory-unit.portable':
  ensure   => '3.0.20171219.105559',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

There are versions of this package awaiting moderation . See the Version History section below.

This package was approved by moderator gep13 on 03 Jun 2019.


Effective memory usage in .NET applications with dotMemory Unit

If you run tests with a standalone unit test runner (rather than Visual Studio) or want to make memory tests a part of your continuous integration builds, then you need a standalone dotMemory Unit launcher - the dotMemoryUnit.exe command-line tool.

dotMemoryUnit.exe works as a mediator - it runs a particular standalone unit test runner and provides the support for dotMemory Unit calls in the running tests.

Check for objects

Checking for objects of a certain type is the main way to locate memory leaks in your code. With dotMemory Unit, you can specify a set of objects by almost any condition, calculate their number and size, and use this information in your assertions.

Check memory traffic

When you need to simply evaluate the amount of memory allocated in a test, you can use the AssertTraffic attribute. This flexible attribute allows you to filter traffic data by object type, interface, or namespace.

Compare snapshots

Like in the dotMemory profiler, you can use checkpoints not only for traffic amount assertions, but also for many kinds of snapshot comparisons.

Continue analysis in dotMemory

Some memory issues will still require further manual investigation in dotMemory. Just set the rules when you want this done, and a workspace for further analysis in dotMemory will be created automatically.

$ErrorActionPreference = 'Stop'; # stop on all errors

$url = ''
$checksum = '02b3463a99d922a431f5ecb3167d2e3473e73b086aed4cb7fb6a811ce5f50ace'

$installPath  = $(Split-Path -parent $MyInvocation.MyCommand.Definition)

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  url           = $url
  UnzipLocation = $installPath
  checksum      = $checksum
  ChecksumType  = 'sha256'

Install-ChocolateyZipPackage @packageArgs

# Exclude ancillory executables from shimming
$files = Get-ChildItem $installPath -Recurse -Include *.exe -Exclude dotMemoryUnit.exe

foreach ($file in $files) {
  New-Item "$file.ignore" -type file -force | Out-Null

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
dotMemory Unit Standalone Launcher (Portable) 3.2.20220510 11 Sunday, July 31, 2022 Ready

This package has no dependencies.

Discussion for the dotMemory Unit Standalone Launcher (Portable) Package

Ground Rules:

  • This discussion is only about dotMemory Unit Standalone Launcher (Portable) and the dotMemory Unit Standalone Launcher (Portable) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or dotMemory Unit Standalone Launcher (Portable), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus