Downloads of v 1.0.5:


Last Update:

23 Oct 2014

Package Maintainer(s):

Software Author(s):

  • Sean Gilbert


Boxstarter frozenbytes development vm sdks

Frozenbytes Baseline Development SDKS

  • 1
  • 2
  • 3

1.0.5 | Updated: 23 Oct 2014



Downloads of v 1.0.5:



Software Author(s):

  • Sean Gilbert

  • 1
  • 2
  • 3
Frozenbytes Baseline Development SDKS 1.0.5

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Unknown

Verification Testing Failed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Frozenbytes Baseline Development SDKS, run the following command from the command line or from PowerShell:


To upgrade Frozenbytes Baseline Development SDKS, run the following command from the command line or from PowerShell:


To uninstall Frozenbytes Baseline Development SDKS, 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 -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 -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
    version: '1.0.5'
    state: present

See docs at

chocolatey_package '' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.0.5'

See docs at

    Name     = ""
    Version  = "1.0.5"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { '':
  ensure   => '1.0.5',
  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 is exempt from moderation. While it is likely safe for you, there is more risk involved.

Boxstarter spec to create baseline windows development machine. This is the third script in a larger set of scripts to create a development vm. Installs VS 2013 SDK, SL 3-5 and Windows 8 SDK.

try {

    # Boxstarter options
    $Boxstarter.RebootOk=$true # Allow reboots?
    $Boxstarter.NoPassword=$false # Is this a machine with no login password?
    $Boxstarter.AutoLogin=$true # Save my password securely and auto-login after a reboot

    # Basic setup
    Update-ExecutionPolicy Unrestricted
    #Silverlight SDKs
    cinst Silverlight3SDK
    if (Test-PendingReboot) { Invoke-Reboot }
    cinst Silverlight4SDK
    if (Test-PendingReboot) { Invoke-Reboot }
    cinst Silverlight5SDK
    if (Test-PendingReboot) { Invoke-Reboot }
    cinst Silverlight5DeveloperRuntime
    if (Test-PendingReboot) { Invoke-Reboot }

    # Visual Studio SDK required for PoshTools extension
    cinst VS2013SDK
    if (Test-PendingReboot) { Invoke-Reboot }

    # Windows SDK 7 or 8
    cinst windows-8-1-sdk
    if (Test-PendingReboot) { Invoke-Reboot }

    Write-ChocolateySuccess ''
} catch {
  Write-ChocolateyFailure '' $($_.Exception.Message)

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
Frozenbytes Baseline Development SDKS 1.0.4 344 Thursday, October 23, 2014 Unknown

October 23 2014 - Revised Release
This is the third script in a larger set of scripts to create a development vm.

3. **

October 22 2014 - Initial Release

VS 2013
Silverlight 3-5 SDK
Windows 8 SDK

This package has no dependencies.

Discussion for the Frozenbytes Baseline Development SDKS Package

Ground Rules:

  • This discussion is only about Frozenbytes Baseline Development SDKS and the Frozenbytes Baseline Development SDKS 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 Frozenbytes Baseline Development SDKS, 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