Creating Packages

Boxstarter includes some commands that can automate a lot of the "grunt" work involved with creating and packing Nuget packages.

Do you really need to create a package?

Maybe not. For simple "One-Off" packages or packages that do not need a home in a public Nuget feed and do not need any additional scripts or resources outside of the ChocolateyInstall.ps1 script, Boxstarter provides a means of creating "on the fly" packages from a single script file or URL. You may pass a file path or URL to the -PackageName parameter of Install-BoxstarterPackage and Boxstarter will generate a temporary package to install the script. If using a URL, the URL content must be plain text and not contain any markup.

Install-BoxstarterPackage -PackageName


The simplest way to create a Nuget package is using the New-PackageFromScript command.

New-PackageFromScript MyScript.ps1 MyPackage

This command takes either a file or http URL (like a Github Gist) that represents the install script. The New-PackageFromScript command will create a Chocolatey Nuget package with the contents of the script moved to the ChocolateyInstall.ps1 file. While this is an incredibly simple way to create a package for your Boxstarter installations, it does not provide much flexibility in customizing the nuspec manifest or adding other files to your install package.


The New-BoxstarterPackage command creates a skeletal package with a minimal *.nuspec file and ChocolateyInstall.ps1 file.

New-BoxstarterPackage -Name MyPackage -Description "I hope you enjoy MyPackage"

This creates a MyPackage.nuspec file that looks like:

<?xml version="1.0" ?>
    <description>I hope you enjoy MyPackage</description>

And a tools/ChocolateyInstall.ps1 with this code:

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

The Boxstarter Local Repository

These files are saved to your local Boxstarter Repository. This is where Boxstarter will store your local packages and running the Install-BoxstarterPackage command will look here first before any external feed. The repository is located in your AppData directory but you can always find out exactly where by inspecting the global Boxstarter variable $Boxstarter.LocalRepo.

You can change the location by using the Set-BoxstarterConfig command:

Set-BoxstarterConfig -LocalRepo "c:\some\other\location"

Editing and adding resources to your package

Optionally, you can call the New-BoxstarterPackage command with a path argument and supply a directory that contains files you want to be included in the package:

    New-BoxstarterPackage -Name MyPackage -Description "I hope you enjoy MyPackage" -Path "c:\somePath"

Boxstarter will copy all files at, and below, c:\somepath and you can refer to these files in your ChocolateyInstall.ps1 using Get-PackageRoot.

Copy-Item (Join-Path -Path (Get-PackageRoot($MyInvocation)) -ChildPath 'console.xml') -Force $env:appdata\console\console.xml

Assuming you have a console.xml file at the root of the path you provided to New-BoxstarterPackage, you can access that file from your ChocolateyInstall.ps1 script.

Composing the ChocolateyInstall Script

If you are already familiar with authoring chocolatey package scripts, you know how to do this already. The only difference with Boxstarter scripts is that your script also has access to Boxstarter's API for configuring windows, running updates as well as logging and reboot control.

Lets open the ChocolateyInstall.ps1 script that the New-BoxstarterPackage command created for our MyPackage package:

Notepad (Join-Path -Path $Boxstarter.LocalRepo -ChildPath "MyPackage\tools\ChocolateyInstall.ps1")

Replace the boilerplate code with something that will actually do something:

Update-ExecutionPolicy Unrestricted
Move-LibraryDirectory "Personal" "$env:UserProfile\skydrive\documents"
Set-ExplorerOptions -showHiddenFilesFoldersDrives -showProtectedOSFiles -showFileExtensions

cinst VisualStudio2013ExpressWeb
cinst fiddler4
cinst mssqlserver2012express
cinst git-credential-winstore
cinst console-devel
cinst poshgit
cinst windbg

cinst Microsoft-Hyper-V-All -source windowsFeatures
cinst IIS-WebServerRole -source windowsfeatures
cinst IIS-HttpCompressionDynamic -source windowsfeatures
cinst TelnetClient -source windowsFeatures

Install-ChocolateyPinnedTaskBarItem "$env:windir\system32\mstsc.exe"
Install-ChocolateyPinnedTaskBarItem "$env:programfiles\console\console.exe"

Copy-Item (Join-Path -Path (Get-PackageRoot($MyInvocation)) -ChildPath 'console.xml') -Force $env:appdata\console\console.xml

Install-ChocolateyVsixPackage xunit
Install-ChocolateyVsixPackage autowrocktestable

Install-WindowsUpdate -AcceptEula

This script does several things and leverage's both Chocolatey and Boxstarter commands. Here is what this will do:

  • Set the PowerShell execution policy to be able to run all scripts
  • Move your personal folders to sync with SkyDrive
  • Make Windows Explorer tolerable
  • Enable Remote Desktop to the box
  • Download and install a bunch of software
  • Enable Windows Features Hyper-V, IIS and the Telnet client
  • Create some shortcuts in the taskbar for common applications
  • Copy your console configuration file with your favorite settings
  • Install some Visual Studio extensions from the Visual Studio gallery
  • Install all critical windows updates

Boxstarter ChocolateyInstall Considerations

Boxstarter can run any Chocolatey package and any valid PowerShell inside that package. However, there are a few things to consider that may make a Boxstarter Chocolatey package a better installation experience.

  • Boxstarter Chocolatey packages should be repeatable. This is especially true if you anticipate the need to reboot. When Boxstarter reboots, it starts running the package from the beginning. So ensure that there is nothing that would cause the package to break if run twice.
  • If you have several Chocolatey packages that you want to install during the Boxstarter session, it is preferable to call CINST directly from inside your ChocolateyInstall instead of declaring them as dependencies. This is because Boxstarter cannot intercept Chocolatey dependencies so those packages will not have any reboot protections.
  • Do not use Restart-Computer or any other command that will reboot the computer. Instead use Invoke-Reboot. This will allow Boxstarter to get things in order first so that after the machine recovers from the reboot, Boxstarter can log the user back in and restart the install script.

Packing your Package .nupkg

Once you are finished composing your package contents, you can call the Invoke-BoxstarterBuild MyPackage command to generate the *.nupkg file for MyPackage. Boxstarter saves these files in the root of $Boxstarter.LocalRepo. If you have several packages in the local repository that you want to build all at once, omit the package name from the command to build all packages in the repository.