Skip to content
This repository
tree: bd661ca3e0
Fetching contributors…

Cannot retrieve contributors at this time

file 61 lines (43 sloc) 3.392 kb

NOTE : Chewie works with as well see below for details

The intent of Chewie is to bring some of the niceties of gems bundler to nuget. Chewie uses a file named .Nugetfile to find all the nugets and you want installed along with how and from where you would like to install them. Chewie is delivered as a set of powershell scripts and a powershell module.

Getting started

Getting Started Video (some function names may have changed) from my friend and Co-Worker Bobby Johnson he also gets credit for the name.
you can either grab the files from here or use nuget (Install-Package Chewie) to get them. The package name is Chewie (amazing I know!).
There are two ways to invoke Chewie. If you are in the PowerShell Console or ISE, Chewie makes the assumption that you have nuget.exe located somewhere in your path. This means that you will need to download it from here. If you are in the Package Manager Console in Visual Studio 2010, Chewie will load itself every time you load a solution in which you installed Chewie and will use the built-in package manager commands.

To create the sample .NugetFile, you can use the following commands to begin working with Chewie.

From the PowerShell Console


From Package Manager Console



Below are some examples of the features in Chewie and how to use them.


usage => source <some_nuget_feed_url>
example => source ''
example => source '' << supports nugit as well

This will set the default source for all of you nugets. Use this if you plan to use some of feed other than the one defined in nuget.exe.


usage => install_to <some_folder_name>
example => install_to 'lib'

This will tell nuget to install the following nugets to the specified folder. Install_To will create the folder if it does not already exist.


usage => version_packages

The default behaviour of Chewie is to put packages into folders that do not include the version number. You can opt out of this behavior and have the default NuGet behavior of versioning folders by adding this to the top of your .NugetFile .


usage => chew [-v/-version ] [-s/-source ]
example => chew 'ninject'
example => chew 'ninject' ''
example => chew 'ninject' -v ''
example => chew 'ninject' '' ''
example => chew 'ninject' -source '' -v ''
example => chew 'nugit-sample-project' -source '' << using nugit as package source

I think you get the idea....

Using the PowerShell Module or Package Manager Console

Using the module is not much different than the script itself except for a couple of changes.

To init a Chewie file once the module is imported you can :

Once you import the module you can get can get chewie doing its thing by calling :

Projects using Chewie

Something went wrong with that request. Please try again.