aliostad/CacheCow — pull request #3 by tugberkugurlu (2012-07-17 08:54:14+00:00)
Title: Nuget package and publish script

Nuget package and publish script has been added.

## Packaging
when you run the build script with the following command, the build will be run and the generated packages will be dropped under *.\artifacts\packages\*.

build.ps1

> For now, I only enabled two projects to be packaged: CacheCow.Common & CacheCow.Server.

## Publishing

When you run it with the following command, the nuget packages will be generated and the generated nuget packages will be pushed to public nuget feed.

build.ps1 -buildTarget /t:DefaultCI

The apiKey needs to be stored as an environment variable. To do that, open up a powershell windows with elevated rights, run the following command (place the proper key before running).

[Environment]::SetEnvironmentVariable("NUGET_API_KEY", "YOUR_API_KEY_HERE", "Machine")

When you open up a new powershell windows, you should see your apiKey with the following command:

$env:NUGET_API_KEY

The beauty here is that you are not manually adding your apiKey every time and you are also not checking it into the source code.

## Versioning and AssemblyInfo File

There is one CommonAssemblyInfo file under *.\src\Common* path. You can control the version here. `AssemblyInformationalVersion` is used by nuget.