A Powershell Module that allows a person to bootstrap NuGet package installation without having to individually install each package manually.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.




This project is to create a PowerShell module that enhances NuGet's package management console and allow for bulk package installation from the console window. Currently, when a person starts a new project in Visual Studio, the developer has to manually install any packages by hand, individually via the Package Management Console prompt or through the Manage Packages dialog window. NuGet.Bootstrapper aims to allow developers to create a packages.config file that represent the packages he or she wishes to install in their new project, run one command, and all of the packages in that file are installed into the project.

Planned Concept

The concept is fairly simple. Like Ruby's Gems, Node's NPM, and Python's PIP, I would like be able able to create a package manifest file that I can add to my .Net projects, type a simple command, and have the packages installed unto my project. Since the Package Manager Console inside of Visual Studio is PowerShell, it makes the most sense to me to create a PowerShell Module that can be installed and ran from that console.

Current Iteration

Since this project is still very young, the PowerShell module isn't ready to be created yet. In it's place is the proof of concept PowerShell script that I'm building from.

(Current) Usage Workflow

  1. Create a new Solution in Visual Studio, and save it.
  2. Copy the NuGet.BootStrapper.ps1 file to the directory where your solution file is.
  3. Add your new Projects to the solution.
  4. Add/Copy the packages.config file containing your standard packages to the project(s).
  5. Open Package Management Console
  6. Make sure you are sitting in your solution directory (by default you should be).
    cd (Split-Path -Parent $dte.Solution.FileName)
  7. .\NuGet.BootStrapper.ps1


The packages.config file should be located in the project directory for which it'll update. It follows the same xml syntax rules as the packages.config file that NuGet maintains normally.

Below is an example of the packages.config file:

<?xml version="1.0" encoding="utf-8"?>
    <package id="Moq" version="4.0.10827" />
    <package id="ShouldFluent" version="" />
    <package id="Unity" version="2.1.505.0" />
    <package id="jQuery" version="1.7.1" />

When the (current) script is ran and finds this file, it'll install the 4 packages automatically for you. In addition, it'll properly add the references to the project file and run any scripts the packages contain that add/update files of the project (i.e. jQuery adds the Scripts directory and adds 3 jQuery scripts into it.).


James Eggers Joshua Poehls