Merge pull request #821 from kenbailey/docs-teamcity

Docs Packaging via TeamCity

docs/using/packaging-tools.md

@@ -12,6 +12,7 @@ The following tools can simplify and/or automate the packaging process.
 * [OctoPack](octopack.md) - steps to use OctoPack to build the source NuGet package to provide to `squirrel --releasify`.
 * [Auto.Squirrel Package Manager](https://github.com/tenacious/Auto.Squirrel) - tool to fully automatize the application deploy, from build to upload the updated files.
 * [Paket](http://fsprojects.github.io/Paket/template-files.html) -  dependency manager for .NET and mono projects, which is designed to work well with NuGet packages and also enables referencing files directly from Git repositories or any HTTP resource.
+* [TeamCity](teamcity.md) - tips on using the TeamCity build server to package your app.  
  
 
 ## See Also

docs/using/teamcity.md

@@ -0,0 +1,22 @@
+| [docs](..)  / [using](.) / teamcity.md
+|:---|
+
+
+# Team City Packaging
+
+
+## Adding the Packaging Step
+
+When TeamCity pulls down your code, the squirrel.exe will sit under packages if it was added to your solution using NuGet.
+
+1. Add a NuGet Pack process which will create the .nupkg based on a .nuspec file to ensure the package is correct.
+2. Create a command line build process and add the following:
+
+~~~
+%system.teamcity.build.workingDir%\packages\squirrel.windows.1.4.0\tools\squirrel --releasify [BUILD_SERVER_NUPKG_PATH]\%system.build.number%.nupkg -r [OUTPUT_PATH]
+~~~
+
+**Note:** Paths may vary depending on your structure so make sure to update the path information above correctly.
+
+This will cause the appropriate files to be created just as if you had run it from the Package Manager Console.
+