Supporting symbols packages from a drop-path.

[Guest]

Currently we build all our Nuget packages to a file-share, and use a Feed Drop Path in ProGet to scan that folder for packages. This works perfectly for .nupkg packages, but it does not pick up symbols packages (.symbols.nupkg).

Any ideas anyone?!

Product: ProGet
Version: 3.7.3

[Guest]

Symbol packages are a little confusing because of the way NuGet builds them. We have updated the ProGet documentation to be more helpful in this regard. See http://inedo.com/support/documentation/proget/feeds/nuget/symbol-and-source-server

If you are putting both the .symbols.nupkg and the .nupkg into the same drop path, then you are likely experiencing the race condition described on that documentation page. ProGet is importing the .nupkg first, then tries to import the .symbols.nupkg. By default, overwriting existing packages from a drop path import is disabled, so the .symbols package is never imported.

In the future, only deploy the symbol package to ProGet; the package without symbols will be produced on demand when necessary. To allow the .symbols packages that you have already copied to the drop path to be imported, you can go to the Admin->Advanced Settings page and change the AllowDropPathImportOverwrite to True, then click Save.

[Guest]

Thanks Dean - that was super helpful :)

I resolved this issue by only promoting the symbols package if one existed.

Many thanks!