Downloads of v


Last Update:

13 Feb 2018

Package Maintainer(s):

Software Author(s):

  • Red Gate Software Ltd


DotNetDeveloperBundle RedGate .NET Developer Bundle profiling admin trial

.NET Developer Bundle

This is not the latest version of .NET Developer Bundle available.

  • 1
  • 2
  • 3 | Updated: 13 Feb 2018



Downloads of v



Software Author(s):

  • Red Gate Software Ltd

  • 1
  • 2
  • 3
.NET Developer Bundle

This is not the latest version of .NET Developer Bundle available.

  • 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


To install .NET Developer Bundle, run the following command from the command line or from PowerShell:


To upgrade .NET Developer Bundle, run the following command from the command line or from PowerShell:


To uninstall .NET Developer Bundle, run the following command from the command line or from PowerShell:


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

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade dotnetdeveloperbundle -y --source="'STEP 3 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 dotnetdeveloperbundle -y --source="'STEP 3 URL'"

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

Exit $exitCode

- name: Ensure dotnetdeveloperbundle installed
    name: dotnetdeveloperbundle
    state: present
    source: STEP 3 URL

See docs at

chocolatey_package 'dotnetdeveloperbundle' do
  action    :install
  version  ''
  source   'STEP 3 URL'

See docs at

    Name: dotnetdeveloperbundle,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller dotnetdeveloperbundle
   Name     = 'dotnetdeveloperbundle'
   Ensure   = 'Present'
   Version  = ''
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'dotnetdeveloperbundle':
  provider => 'chocolatey',
  ensure   => '',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install dotnetdeveloperbundle version="" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator gep13 on 05 Apr 2018.


The .NET Developer Bundle includes:

  • ANTS Performance Profiler Pro - Get a complete picture of your application's performance and find bottlenecks, whether in the code or database.
  • ANTS Memory Profiler - Find memory leaks within minutes and optimize the memory usage of your C# and VB.NET code.
  • .NET Reflector VSPro - Understand and debug any 3rd party code, including frameworks, components and libraries.

Package Download Fallback

This package will fallback to the Red Gate FTP site once the main fixed URL no longer matches the version for which this package was created. This is to ensure that a specific version of the Chocolatey package continues to work even after Red Gate releases newer versions.

When a newer version of the package is published, it will then revert to using the primary https download URL.

Package Parameters

The following package parameters can be set:

  • /FTP - Force using the FTP download URL

These parameters can be passed to the installer with the use of --params.
For example: --params "'/FTP'".

$ErrorActionPreference = 'Stop';
$toolsDir     = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$checksum = '603B40203ECBD02ED94473AA45968798B4CECC5F6C3D5C8B614AC72D440A0E83'
$primaryDownloadUrl = ''
$secondaryDownloadUrl = ''
$packageVersionLastModified = New-Object -TypeName DateTimeOffset 2018, 2, 12, 13, 32, 54, 0 # Last modified time corresponding to this package version

$pp = Get-PackageParameters

if ($pp["FTP"] -ne $null -and $pp["FTP"] -ne '') { 

  # FTP forced  
    $url = $secondaryDownloadUrl
} else {

  # Red Gate have a fixed download URL, but if the binary changes we can fall back to their FTP site
  # so the package doesn't break
  $headers = Get-WebHeaders -url $primaryDownloadUrl
  $lastModifiedHeader = $headers.'Last-Modified'

  $lastModified = [DateTimeOffset]::Parse($lastModifiedHeader, [Globalization.CultureInfo]::InvariantCulture)

  Write-Verbose "Package LastModified: $packageVersionLastModified"
  Write-Verbose "HTTP Last Modified  : $lastModified"

  if ($lastModified -ne $packageVersionLastModified) {
    Write-Warning "The download available at $primaryDownloadUrl has changed from what this package was expecting. Falling back to FTP for version-specific URL"
    $url = $secondaryDownloadUrl
  } else {
    Write-Verbose "Primary URL matches package expectation"
    $url = $primaryDownloadUrl

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  fileType      = 'exe'
  silentArgs    = "/IAgreeToTheEULA"
  validExitCodes= @(0)
  url           = $url
  checksum      = $checksum
  checksumType  = 'sha256'
  destination   = $toolsDir

Install-ChocolateyPackage @packageArgs
$ErrorActionPreference = 'Stop';

# Empty placeholder uninstall script so that Chocolatey doesn't get confused by not being able to match the package name
# Auto-uninstall correctly uninstalls all individual applications in this bundle

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.

Version Downloads Last Updated Status
.NET Developer Bundle 2020.11.23 49 Wednesday, November 25, 2020 Approved
.NET Developer Bundle 2020.11.18 25 Friday, November 20, 2020 Approved
.NET Developer Bundle 2020.10.15 71 Saturday, October 17, 2020 Approved
.NET Developer Bundle 2020.10.14 21 Friday, October 16, 2020 Approved
.NET Developer Bundle 2020.09.16 66 Friday, September 18, 2020 Approved
.NET Developer Bundle 2020.09.03 64 Saturday, September 5, 2020 Approved
.NET Developer Bundle 2020.08.12 79 Friday, August 14, 2020 Approved
.NET Developer Bundle 2020.07.29 49 Friday, July 31, 2020 Approved
.NET Developer Bundle 2020.07.13 48 Wednesday, July 15, 2020 Approved

Discussion for the .NET Developer Bundle Package

Ground Rules:

  • This discussion is only about .NET Developer Bundle and the .NET Developer Bundle 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 .NET Developer Bundle, 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