Downloads:

423,366

Downloads of v 12.0.21005.1:

1,424

Last Update:

11 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.

12.0.21005.1 | Updated: 11 Apr 2014

Downloads:

423,366

Downloads of v 12.0.21005.1:

1,424

Maintainer(s):

Software Author(s):

  • Microsoft Corporation

Microsoft Build Tools 2013 12.0.21005.1

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

All Checks are Unknown

2 Test of Unknown Status


Validation Testing Unknown


Verification Testing Unknown

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:

>

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 https://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. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade microsoft-build-tools -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 microsoft-build-tools -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure microsoft-build-tools installed
  win_chocolatey:
    name: microsoft-build-tools
    state: present
    version: 12.0.21005.1
    source: STEP 3 URL

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

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'microsoft-build-tools' do
  action    :install
  version  '12.0.21005.1'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: microsoft-build-tools,
    Version: 12.0.21005.1,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller microsoft-build-tools
{
   Name     = 'microsoft-build-tools'
   Ensure   = 'Present'
   Version  = '12.0.21005.1'
   Source   = 'STEP 3 URL'
}

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


package { 'microsoft-build-tools':
  provider => 'chocolatey',
  ensure   => '12.0.21005.1',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install microsoft-build-tools version="12.0.21005.1" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. 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

Microsoft Build Tools 2013


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
Microsoft Build Tools for Visual Studio 2017 15.0.26228.0 27206 Thursday, March 16, 2017 Approved
Microsoft Build Tools 2015 Update 3 14.0.25420.1 107699 Tuesday, July 19, 2016 Approved
Microsoft Build Tools 2015 Update 2 14.0.25123.0 69610 Tuesday, June 14, 2016 Approved
Microsoft Build Tools 2015 14.0.23107.10 18146 Sunday, August 23, 2015 Approved
Microsoft Build Tools 2013 12.0.21005.20140416 146681 Wednesday, April 16, 2014 Approved
Microsoft Build Tools 2013 12.0.21005.1 1424 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