Hi To recap for future reference. To push a package containing symbols and sourcecode the following has been tested and worked fine with nuget 2.8: Create nuget package using: nuget pack foo.csproj -Symbols Alternatively use: nuget pack foo.spec -Symbols The above command will create two nupkg. The one decorated with the word symbols does contain all libs as well as the sourcecode and PDB files. You cna check yourselfes by opening hte nupkg in something like winzip or 7zip, since the package is basically a zip file. Push the symbols package to proget. check the package on the feed. If the symbols server is activated the package info will show that symbols and source are available. Follow the Inedo guide on how to add The Proget symbol server support into Visual Studio. Food for thought. My, very quick test, shows me that a package build in the .NET 4.0 framework, of course works fine in a .NET 4.5 project, but i could not use the symbols to debug. I tried to remove the package, downgrade my test project to .NET 4.0 and reinstall the package. Now i could debug nicely into the source. Bottomline. The symbols package and the project that uses it must be on the same .NET version for the symbols to work. Symbols compatibility does, apparently, not span framework versions, even thou the frameworks themselves are backwards compatible. Thomas

@Tod,@Calvin I've tested it in 3.5.3 and it works now. Thanks!

We managed to resolve this - it turns out that the proget feeds were being ignored because the version of proget was not compatible with NuGet 2.7.1. An update to the latest version of ProGet resolved the issue. Thanks for the response though! :)

I am sorry. The package that still caused problems had a version number like 3.40.0000.0. This seems to bother a nuget 2.7 client, but not a nuget 2.6 client. The problem disappeared when rebuilding the package using the 3.40.0.0 version number.

Every .NET project that consumes NuGet packages has a packages.config file, and that should be in source control. Unless I'm missing something, the deployment plan actions should be as simple as "Getting Latest" from TFS, then an "Install NuGet Packages" action followed by "Create NuGet Package".

Can you try to use the "Build .NET Project" without checking "this is a web application"? Then, capture the artifact from _PublishedWebsites\project.name instead? This is how we solve this problem when we build proget (see http://inedo.com/specifics/proget), and we'll soon be adding another option for this action.

I think so, Gary. Thanks again for the pointers. I'll be sure to ask if I have any more questions. Have a great day! Matthew