Downloads of v 1.0.2:


Last Update:

22 Apr 2013

Package Maintainer(s):

Software Author(s):

  • Michael Field
  • Ethan Brown


devbox admin path binroot

Devbox Common Settings

  • 1
  • 2
  • 3

1.0.2 | Updated: 22 Apr 2013



Downloads of v 1.0.2:



Software Author(s):

  • Michael Field
  • Ethan Brown

  • 1
  • 2
  • 3
Devbox Common Settings 1.0.2

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Unknown

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Devbox Common Settings, run the following command from the command line or from PowerShell:


To upgrade Devbox Common Settings, run the following command from the command line or from PowerShell:


To uninstall Devbox Common Settings, 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 devbox-common -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 devbox-common -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 devbox-common
    name: devbox-common
    version: '1.0.2'
    state: present

See docs at

chocolatey_package 'devbox-common' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.0.2'

See docs at

cChocoPackageInstaller devbox-common
    Name     = "devbox-common"
    Version  = "1.0.2"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'devbox-common':
  ensure   => '1.0.2',
  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 submitted prior to moderation and has not been approved. While it is likely safe for you, there is more risk involved.


This package performs miscellaneous actions to customize your command line experience.

1. Set environment variable « chocolatey_bin_root » to C:\Tools, only if it's not already set. Some packages that would otherwise install into system root will look for this variable. Packages that behave in this way are: Ruby, Python etc - almost any package that is not comfortable with spaces in filenames.
2. Permanently sets HOME environment variable to a valid value, if not already set.
3. Installs « setenv » command that refreshes environment variables without the need to restart command shell. Sometimes very useful.
4. Establishes a flexible system of auto-run include files, specified in user's home directory. After that, any file residing in home directory looking like « .bashrc.include.*.bat » gets auto-executed at every command shell start.

Automatic uninstall procedure is included in this package, so you don't need to manually reverse whatever actions installer did. This procedure will unset « chocolatey_bin_root » variable (1.) but will not do anything to remove effects of (2.), (3.) and (4.) because these settings are very unobtrusive.

NOTE: Phrase « Devbox » in a name of this package is used as signature to indicate high quality standards. Functionally, the package is the same as any other Chocolatey package.

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

Fix setenv.bat

Discussion for the Devbox Common Settings Package

Ground Rules:

  • This discussion is only about Devbox Common Settings and the Devbox Common Settings 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 Devbox Common Settings, 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