Proget strips config files from packages

Dear Inedo,

We're using the free version of your Proget product as our in-house NuGet server. The extra features that ProGet adds are really usefull when you want more then just a plain feed.

We're also using the built-in source and symbol service that your product provides.

However, it appears that somewhere from publishing the package to ProGet to downloading it in Visual Studio .config files are being stripped out of the package. We want to include an example config file with one of our packages and looking at the output from TeamCity (where the package is built) the config file in inside the content folder.

Can you help us with this? If needed I can send the Nuspec files and/or the package files.

Thanks in advance,

Floris Robbemont

Product: ProGet
Version: 3.5.6

That's strange. The only files ProGet can remove from a package are .pdb files, and that functionality can be disabled at the feed level. The first thing to try would be to download the package file from the web UI instead of using Visual Studio/NuGet, then open it in 7-zip or NuGet package explorer. If the config files are there, it's not a ProGet issue, since that's the exact same URL that Visual Studio and NuGet use to download the package. In that case you may want to try clearing your local NuGet package cache from Visual Studio.

Does this help?

Hi Dean,

I have already tried that. The package output (before it's published to ProGet) contains the config file in the /content folder. But when I try downloading it from Proget the entire content folder is removed from the package.

It's not a normal package though. The package only contains Msbuild scripts in the /build folder, and nothing else. Could that be the reason the config file is removed?

ProGet does not strip these files; you can verify this by creating a package manually, then adding it manually, then downloading it manually.

It would be NuGet (or whatever tool you're using to package) that is stripping the files -- when you find out exactly what's wrong, please share in case someone else finds this issue.

It seems to be an issue with TeamCity. For some reason.. the packages it creates all have the config files, but when it publishes them to ProGet the files get stripped out.

I've tested this with a manual nuget.exe push to ProGet, and then the package seems fine.

I'm hoping this is some setting in TeamCity that can be changed. I'll contact them for further support.

The story continuous :)

Because I set TeamCity to create source packages as well (it's a checkbox called: Include sources and symbols) it was overwriting the packages in ProGet (I have all the PDB and sources in my nuspec files as well).

This was causing the issue with the config file being gone, because TeamCity strips those files out for the symbols packages.

So... I was doing things twice...
Must be user error ;)