First things first. There is no overall DeltaShell solution file anymore that contains both framework and products. That means that a framework developer cannot easily check which classes are actually used by the products. This is a flaw in our work process and should be fixed as soon as possible.

...

The NuGet specifications can be found in svn under trunk/Framework/sdk. I'm not going into detail at the moment on how these specifications work. There is enough reference material on the interwebz. There are two folders in the sdk folder. packages and tools. The tools folder contains some utility functions that can be useful during the install.ps1 script that is run when the NuGet package is installed into the csproj.

Building and Testing NuGet

...

When you change something in the framework and you want to see if the supported products don't have any issues, you will have to manually update the supported products on your local machine. Then run a couple of tests or let TeamCity run the tests as a personal build. You don't want TeamCity to build your NuGet packages every time. It is way faster when you do it locally.

You can create an example NuGet package that the build server would normally make via trunk/Framework/sdk/nuget pack commands.bat. It will generate your packages that you can then install in one of the products for testing purposes.

...