Downloads:

738,172

Downloads of v 12.0.21005.20140416:

212,838

Last Update:

16 Apr 2014

Package Maintainer(s):

Software Author(s):

  • Microsoft Corporation

Tags:

Microsoft Build Tools 2013 MSBuild Compiler

Microsoft Build Tools 2013

This is not the latest version of Microsoft Build Tools 2013 available.

  • 1
  • 2
  • 3

12.0.21005.20140416 | Updated: 16 Apr 2014

Downloads:

738,172

Downloads of v 12.0.21005.20140416:

212,838

Maintainer(s):

Software Author(s):

  • Microsoft Corporation

  • 1
  • 2
  • 3
Microsoft Build Tools 2013 12.0.21005.20140416

This is not the latest version of Microsoft Build Tools 2013 available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Unknown


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Microsoft Build Tools 2013, run the following command from the command line or from PowerShell:

>

To upgrade Microsoft Build Tools 2013, run the following command from the command line or from PowerShell:

>

To uninstall Microsoft Build Tools 2013, 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 https://community.chocolatey.org/api/v2/)


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 https://community.chocolatey.org/api/v2/. 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 microsoft-build-tools -y --source="'INTERNAL REPO URL'" --version="'12.0.21005.20140416'" [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 microsoft-build-tools -y --source="'INTERNAL REPO URL'" --version="'12.0.21005.20140416'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install microsoft-build-tools
  win_chocolatey:
    name: microsoft-build-tools
    version: '12.0.21005.20140416'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'microsoft-build-tools' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '12.0.21005.20140416'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller microsoft-build-tools
{
    Name     = "microsoft-build-tools"
    Version  = "12.0.21005.20140416"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'microsoft-build-tools':
  ensure   => '12.0.21005.20140416',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 17 Apr 2017.

Description

If you don't have Visual Studio installed on your computer, you can use Build Tools 2013 to build managed applications. The Visual Basic and C# compilers are also included in this download. (In earlier versions, these tools were included in the stand-alone .NET Framework.)


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
Microsoft Build Tools for Visual Studio 2017 15.0.26228.0 28150 Thursday, March 16, 2017 Approved
Microsoft Build Tools 2015 Update 3 14.0.25420.1 287103 Tuesday, July 19, 2016 Approved
Microsoft Build Tools 2015 Update 2 14.0.25123.0 69933 Tuesday, June 14, 2016 Approved
Microsoft Build Tools 2015 14.0.23107.10 29385 Sunday, August 23, 2015 Approved
Microsoft Build Tools 2013 12.0.21005.20140416 212838 Wednesday, April 16, 2014 Approved
Microsoft Build Tools 2013 12.0.21005.1 2131 Friday, April 11, 2014 Approved

This package has no dependencies.

Discussion for the Microsoft Build Tools 2013 Package

Ground Rules:

  • This discussion is only about Microsoft Build Tools 2013 and the Microsoft Build Tools 2013 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 Microsoft Build Tools 2013, 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