Downloads of v 3.5.20160716:


Last Update:

17 Jul 2016

Package Maintainer(s):

Software Author(s):

  • Microsoft


Microsoft .net Framework 3.5

Dot Net 3.5

  • 1
  • 2
  • 3

3.5.20160716 | Updated: 17 Jul 2016



Downloads of v 3.5.20160716:



Software Author(s):

  • Microsoft

  • 1
  • 2
  • 3
Dot Net 3.5 3.5.20160716

  • 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 Dot Net 3.5, run the following command from the command line or from PowerShell:


To upgrade Dot Net 3.5, run the following command from the command line or from PowerShell:


To uninstall Dot Net 3.5, 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 dotnet3.5 -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 dotnet3.5 -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 dotnet3.5
    name: dotnet3.5
    version: '3.5.20160716'
    state: present

See docs at

chocolatey_package 'dotnet3.5' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '3.5.20160716'

See docs at

cChocoPackageInstaller dotnet3.5
    Name     = "dotnet3.5"
    Version  = "3.5.20160716"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'dotnet3.5':
  ensure   => '3.5.20160716',
  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.

This package was approved by moderator doc on 17 Jul 2016.


This installs the .net framework version 3.5 (includes versions 2.0 and 3.0). This package does not directly download any software. It uses the Windows Features and functionality of the operating system to enable the feature. Depending on your OS version, it may download this software via the windows update service. You may want to use this package as a dependency package for packages requiring .net 3.5. If .net 3.5 is already enabled or installed, this package will do nothing.

if(-not (test-path "hklm:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5")) {
  if((wmic os get caption | Out-String).Contains("Server")) {
      $packageArgs = "/c DISM /Online /NoRestart /Enable-Feature /FeatureName:NetFx3ServerFeatures"
      $statements = "cmd.exe $packageArgs"
      Start-ChocolateyProcessAsAdmin "$statements" -minimized -nosleep -validExitCodes @(0, 1)
  $packageArgs = "/c DISM /Online /NoRestart /Enable-Feature /FeatureName:NetFx3"
  $statements = "cmd.exe $packageArgs"
  Start-ChocolateyProcessAsAdmin "$statements" -minimized -nosleep -validExitCodes @(0)
else {
     Write-Host "Microsoft .Net 3.5 Framework is already installed on your machine."

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
Dot Net 3.5 3.5.20160218 18732 Friday, February 19, 2016 Approved
Dot Net 3.5 3.5.20160216 1637 Tuesday, February 16, 2016 Approved
Dot Net 3.5 3.5.20160211 2085 Friday, February 12, 2016 Approved
Dot Net 3.5 3.5.20160116 3534 Sunday, January 17, 2016 Approved
Dot Net 3.5 3.5.20140403 33565 Thursday, April 3, 2014 Approved
Dot Net 3.5 3.5 4192 Sunday, October 27, 2013 Unknown

This package has no dependencies.

Discussion for the Dot Net 3.5 Package

Ground Rules:

  • This discussion is only about Dot Net 3.5 and the Dot Net 3.5 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 Dot Net 3.5, 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