The goal of this project is to provide a central place to share ideas for streamlining dev box setup and provide sample scripts for common dev scenarios. It's likely you will want to take the scripts here and modify them to fit your particular needs. When you make those changes if you think others would benefit please consider submitting a PR. Before you contribute please see the Contribution Guidelines.
These scripts leverage two popular open source projects.
- Boxstarter boxstarter.org
- Chocolatey chocolatey.org
Boxstarter is a wrapper for Chocolatey and includes features like managing reboots for you. We're using the Boxstarter web launcher to start the installation process:
https://boxstarter.org/Learn/WebLauncher
The script code is organized in a hierarchy
Recipes A recipe is the script you run. It calls multiple helper scripts. These currently live in the root of the project (dev_app.ps1, dev_webnodejs.ps1, etc.)
Helper Scripts: A helper script performs setup routines that may be useful by many recipes. Recipes call helper scripts (you don't run helper scripts directly). The helper scripts live in the scripts folder
These scripts should cover a lot of what you need but will not likely match your personal preferences exactly. In this case please fork the project and change the scripts however you desire. We really appreciate PR's back to this project if you have recommended changes.
Note: The one-click links use the following format. When working out of a different Fork or Branch you'll want to update the links as follows:
http://boxstarter.org/package/url?https://raw.githubusercontent.com/GITHUB_DOMAIN/windows-dev-box-setup-scripts/YOUR_BRANCH/RECIPE_NAME.ps1
For more info on testing your changes take a look at the contribution guidelines.
Before you begin, please read the Legal section.
To run a recipe script, click a link in the table below from your target machine. This will download the Boxstarter one-click application, and prompt you for Boxstarter to run with Administrator privileges (which it needs to do its job). Clicking yes in this dialog will cause the recipe to begin. You can then leave the job unattended and come back when it's finished.
| Click link to run | Description |
|---|---|
| Full Desktop App | Windows Desktop App Development (Visual Studio, Windows SDK, C++, UWP, .NET (WPF and Winforms)) |
| UWP Desktop App | Windows Desktop App Development (Visual Studio, Windows SDK, UWP) |
| .NET Desktop App | Windows Desktop App Development (Visual Studio, Windows SDK, .NET (WPF and Winforms)) |
| C++ Desktop App | Windows Desktop App Development (Visual Studio, Windows SDK, C++) |
| Web | Web (VS Code, WSL, Multiple Browsers) |
| Web NodeJS | Web Dev with NodeJS (Web + NodeJS LTS)¹ |
| Machine Learning Windows | Machine Learning with only Windows native tools |
| Machine Learning Linux | Machine Learning with Linux tools running on WSL |
| DevOps Azure | Client setup for DevOps with Azure |
| Xamarin (Visual Studio, Xamarin, Android SDK) | |
| Containers (Docker, Kubernetes, etc...) | |
| Submit a PR with a recommended configuration! |
Notes:
- If you are using WSL there's a followup step we recommend after running the setup script. When the script finishes you will only have a root user with a blank password. You should manually create a non-root user via
$ sudo adduser [USERNAME] sudowith a non-blank password. Use this user going forward. For more info on WSL please refer to the documentation. - If you're a Node.js contributor working on Node.js core, please see the Node.js Bootstrapping Guide or click here to run.
- The Boxstarter ClickOnce installer does not work when using Chrome. This issue is being tracked here. Please use Edge to run the ClickOnce installer.
- Reboot is not always logging you back in to resume the script. This is being tracked here. The workaround is to login manually and the script will continue running.
- There have been reports of Windows 1803 not successfully launching Boxstarter via the web launcher. See this issue for details: chocolatey/boxstarter#301
As an organization, you may not be keen to reach out to the internet. That's fine as with just a few modifications you can still take advantage of these scripts. Visit the organizational use page to learn how.
In a classroom setting it's a great idea to give your students a recipe script so they can all get setup quickly and reliably. You can modify your recipe script to include downloading course materials and sample projects. To do this, start by forking this project and follow the instructions here.
Are you in an environment where you don't have any administrative access on your machine? No problem, you can still take advantage of Chocolatey and manage "portable" software. You can also use a VM where you may have administrative access (see next section).
Unfortunately some of Boxstarter's functionality does require administrative privileges to run, and it will prompt to elevate to administrator if not already elevated.
So while you won't be able to use Boxstarter, take a look at Chocolatey's documentation on Non-Administrative Install. There you will find resources and an example PowerShell script that gives you a quick setup of Chocolatey and installation of a few packages. While not full on Boxstarter, you are still going to get a pretty rapid setup!
NOTE: It's important to point out the open source edition of the Chocolatey client will not allow you to magically install software that requires administrative access, so you will need to find packages that are portable or create those and push them to the community repository or your internal sources.
Windows 10 VM setup instructions
- Use Hyper-V's Quick Create to set up a VM
- Once signed in to your VM, visit this project in a web browser and click one of the script links in the Readme
Please read before using scripts.
When you use our sample scripts, these will direct to Chocolately to install the packages. By using Chocolatey to install a package, you are accepting the license for the application, executable(s), or other artifacts delivered to your machine as a result of a Chocolatey install. This acceptance occurs whether you know the license terms or not. Read and understand the license terms of any package you plan to install prior to installation through Chocolatey. If you do not want to accept the license of a package you are installing, you need to uninstall the package and any artifacts that end up on your machine as a result of the install.
Chocolately has implemented security safeguards in their process to help protect the community from malicious or pirated software, but any use of our scripts is at your own risk. Please read the Chocolately's legal terms of use and the Boxstarter project license as well as how the community repository for Chocolatey.org is maintained.
Our project is subject to the MIT License and we make no warranties, express or implied of any kind. In no event is Microsoft or contributing copyright holders be liable for any claim, damages or other liability arising from out of or in connection with the use of the project software or the use of other dealings in the project software.
Do you want to contribute? We would love your help. Here are our contribution guidelines.
