Symbol Server for portable pdb

christian_panten

Hi,

if I take a look on the result of link I can see this section
which I am missing in the corresponding link to our ProGet feed.

Could this the reason why nuget push -source symbols-feed MyPackage.1.2.0.snupkg
is failing?

Best regards
Christian

rhessinger

Hi @christian_panten,

Can you please send over the error you are seeing when running nuget push? As long as your -Source is the NuGet API URL, then you shouldn't need to do anything special.

Thanks,
Rich

christian_panten

@rhessinger

here is a screen shot of my push.

as you can see:

pushing nupkg to packages feed works fine
pushing snupkg to packages feed failed
pushing snupkg to symbols feed failed too

Best regards
Christian

rhessinger

Hi @christian_panten,

Are there any errors showing in the Diagnostics center?

Thanks,
Rich

christian_panten

@rhessinger,

No there are no messages.

Best regards
Christian

atripp

First off, if you want to have separate library and symbols packages (which we don't recommend), then you'll need to make a separate symbols feed. ProGet supports a "combined package" and will strip out symbols/source unless explicitly requested, so you don't have to bother.

But if you want to separate, please note that nuget is a "little" funny. If the file extension ends in .snupkg then it ignores the source argument, and attempts to push the file to Microsoft's server (symbols.nuget.org).

This is because symbol packages and regular packages must be pushed to a different feed. If you want to specify a custom symbols feed, then please use the --symbol-source when using a .snupkg file.

@christian_panten I have a favor.... can you suggest (or do a pull request) on how we can update our documentation to make this more clear? Thanks

christian_panten

Hi @atripp,

your proposal to use --symbol-source does not work with .snupkg. As you can see there is an
exception pushing only the snupkg file.

Also pushing both files at the same time is pushing only the nupkg.

I don't have any idea how to continue. Do you have further steps to try?

Were you able to run the same tests on your machines?

Best regards
Christian

atripp

@christian_panten as I mentioned, we recommend making a single symbol package to avoid this kind of headache (it changes between versions of nuget CLI ), and I don't use nuget.exe to push packages in this manner so I can't say it

If you were to just upload or PUT the package to ProGet, then it would work fine. So we are just trying to figure out nuget.exe's quirks, and why he refuses to push to a custom symbol source...

The screenshot you showed seems to be fine. I also read the nuget.exe push documentation.

I don't think you're supposed to specify the snupkg file. I believe he will search for a .snupkg and then push it? It's hard for a guess.

I also remember this was broken for a while in nuget.exe (not using of SymbolApi at all), but it works in dotnet push.

christian_panten

@atripp

We are not using proget as default nuget package source.
Our company decided to use artifactory as nuget repository.
So, we don't want to create nuget packages including the pdb files.

I would like to find out if the symbol server of proget is able to
provide us the portable pdb files.

Currently, including the pdbs in the original nuget package seams to
work. But it's not an option for us.

There is no command: dotnet push

And dotnet nuget push does also not work. Same issue as nuget.exe.

How can we proceed?

Best regards
Christian

atripp

I think dot net publish, but remember these are really meant to work with nuget.org. This might be an issue to take up with the NuGet team; it's very possible their tool doesn't support this use case and is buggy.

It's just an HTTP PUT, so you could do it in a line of PowerShell as well using the Invoke-RestMethod CmdLet: Invoke-RestMethod -Uri $uri -Method Post -InFile $uploadPath

Here is some more information from NuGet's docs: https://docs.microsoft.com/en-us/nuget/api/package-publish-resource#push-a-package

christian_panten

@atripp

I will try to use the API directly to test if it works.

dotnet publish is not the command to publish a nuget package. It is use
to restore nuget dependencies, to build a project and to copy all required
files to a separate folder.

Next to your provided link there is a documentation how to push snupkg files.
And as you can see here, it depends on SymbolPackagePublish resource found in the service index.
But this resource is missing in the service index delivered by our proget installation. Maybe this could be
a hint for you which can help solving my issue.

I will let you know if the direct usage of the API solves also my issue.

Many thanks for you support.

Best regards
Christian

christian_panten

@atripp

UPDATE:

I was able to use curl to upload the snupkg symbols package via:

curl -v -i -X PUT -H 'X-NuGet-ApiKey: xxx' -F 'file=@./Trimble.MEP.MyPackage.1.4.0.snupkg;' http://localhost/nuget/symbols/package

Best regards
Christian

christian_panten

Since there is no further update and no solution for my problem using nuget cli or dotnet cli I am closing this thread.

jonathon.hameier_4326

This post is deleted!