@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

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

@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

@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

@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

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

@rhessinger,

No there are no messages.

Best regards
Christian

@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

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

Hi @rhessinger,

I don't know why, but using this push does not work for me.
I don't see any response and the package is not uploaded.

Did you try it?

Best regards
Christian

Hi @rhessinger,

I run proget on windows and configured a separate feed for the symbol nuget
packages. I enabled Symbol Server functionality for this feed.

http://proget:8624/nuget/sýmbol-feed/v3/index.json

My nuget config looks like this:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <activePackageSource>
    <add key="nuget.org" value="https://www.nuget.org/api/v2/" />
  </activePackageSource>
  <packageRestore>
    <add key="enabled" value="True" />
    <add key="automatic" value="True" />
  </packageRestore>
  <packageSources>
    <add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
    <add key="symbols-feed" value="http://proget:8624/nuget/symbols-feed/v3/index.json" />
    <add key="packages-feed" value="http://proget:8624/nuget/packages-feed/v3/index.json" />    
  </packageSources>
  <bindingRedirects>
    <add key="skip" value="False" />
  </bindingRedirects>
  <apikeys>
    <add key="http://proget:8624/nuget/symbols-feed/v3/index.json" value="AQAAANxxxxxxxxxxxxxxxxxxxxx==" />
    <add key="http://proget:8624/nuget/packages-feed/v3/index.json" value="AQAAANxxxxxxxxxxxxxxxxxxxxx==" />
  </apikeys>
<packageSourceCredentials>
 <symbols-feed>
  <add key="Username" value="Example" />
  <add key="ClearTextPassword" value="Pwd" />
 </symbols-feed>
 <packages-feed>
  <add key="Username" value="Example" />
  <add key="ClearTextPassword" value="Pwd" />
 </packages-feed>
</packageSourceCredentials>
  <packageManagement>
    <add key="format" value="0" />
    <add key="disabled" value="False" />
  </packageManagement>
  <disabledPackageSources>
  </disabledPackageSources>
</configuration>

Now I build my package using:

dotnet pack -c Release

This results in:

MyPackage.1.2.0.nupkg
MyPackage.1.2.0.snupkg

Using nuget I can push the package to proget:

nuget push -source packages-feed MyPackage.1.2.0.nupkg

This works well.

But how can I push the snupkg to proget feed symbols-feed?

Best regards
Christian