Pushing symbols to proget symbol feed

csi_lund

Hi
I was wondering if anyone could help me with an issue regarding pushing symbol packages to a proget nuget symbols feed.
Essentially im packing the project and including symbols and then running this command.

dotnet nuget push [packagename].nupkg --source https://packages.[packageserver].com/nuget/nuget/ --symbol-source https://packages.[packageserver].com/symbols/nuget --api-key '********'

but what I find is that nuget appends a trailing "/" to the symbol URL (ive tried with just the regular nuget push *.nupkg ...... as well to confirm its not a dotnet command issue).

What I get in the response is:

Pushing [packageName].symbols.nupkg to 'https://[packageserver]/symbols/nuget'...
PUT https://packages. [packageserver].com/symbols/nuget/
NotFound https://packages. [packageserver].com/symbols/nuget/ 104ms
error: Response status code does not indicate success: 404 (Not Found).

This matches the behaviour if I navigate to the url in a browser; navigating to https://packages.[packageserver].com/symbols/nuget/ gets the 404 and error page

navigating to https://packages.[packageserver].com/symbols/nuget without the trailing slash - works (or well I get the Obi Won page "If you've visited this URL to diagnose why they aren't serving correctly, here are some tips:"). This additional slash is also appended to the source feed url if without however this resolves since this matches the feed url.

Is there a way to change the symbols package feed url so its consistent with the feed and works with the trailing slash? When I look at the configuration I change properties but not the feed url. And I can see anyway to do so.

NanciCalo

Hi @csi_lund

We recently updated our documentation, can you take a read at Symbol and Source Server in ProGet?

Hopefully it helps explain things, but a couple things that are jumping out

the /symbols/<feed-name> end point is intended for Visual Studio; you can't push packages to it, and will need to push to /nuget/<feed-name>
if you want to use a single feed, then you need to make a single package by setting the DebugType property on your project file to embedded

Please let me know if I can clarify, so then we can improve our docs as well :)

Nanci

patrick.groess_2616

Hi Nanci,

I've exactly the same problem.

The problem is, that nuget automatically adds an trailing slash. So while do the following:

nuget push MyPackage.symbols.nupkg -Source http://MyServer:8624/symbols

nuget adds an trailing slash http://MyServer:8624/symbols/

And while http://MyServer:8624/symbols is working fine, http://MyServer:8624/symbols/ throws an 404 error.
So to use ProGet Symbol Server in a .NET environment would require a behaviour change in ProGet.

It's not hosted in IIS, if that relevant.

atripp

Hi @patrick-groess_2616 ,

The /symbols/<feed-name> URL is only for Visual Studio's Symbol Location setting, and is used to download symbols. Do not try to use it with nuget.exe, it will give that error.

You need to use /nuget/<feed-name> to push symbol or nuget.exe packages.

Thanks,
Alana