With Web projects, using Nuget packages seems to work normally - but when I attempt to pack up a Windows Service, I get the familiar error “NuGet packages with dependencies are not currently supported.” - with or without using OctoPack.
I’ll try to reproduce this and release a fix tonight.
In the mean time the problem is likely to be the existence of a packages.config file. In the packages.config property window in Visual Studio, make sure ‘Build Action’ is ‘None’ and ‘Copy to Output Directory’ is ‘Do not copy’. If that doesn’t solve it, OctoPack might need to be extended to automatically rename the file before packaging and revert it back afterwards.
I think I know why. It all works great until you want to use static libraries. The issue seems to be with OctoPack - it doesn’t want to include any of them, even if they are set to CopyLocal. If I try and specify them in the nuspec, it’ll override OctoPack.
When I build in release, all the files are in the root (no content/lib directories) - though when it gets run through TeamCity, all seems right except that the static libraries aren’t there.