title: Does nuget push to Azure DevOps artifact include symbols?
body: <p>I have a class library that I often need to debug/step-into that I distribute and use as a nuget package to Azure DevOps Artifacts feed.  </p>
  
  <p>To create the package, I run the following commands using nuget.exe v5.4:</p>
  
  <pre class="lang-bsh prettyprint-override"><code>nuget spec
  </code></pre>
  
  <p>I then enter data in the .nuspec file.  Then I run:</p>
  
  <pre class="lang-bsh prettyprint-override"><code>nuget pack myLibrary.csproj -Symbols -SymbolPackageFormat snupkg
  </code></pre>
  
  <p>This generates both the nuget package file and the snupkg symbol file in the current working directory.</p>
  
  <p>I then push this up to our Artifacts feed using the VSTS Credential Provider:</p>
  
  <pre class="lang-bsh prettyprint-override"><code>nuget push -Source "MyPackageSource" -ApiKey VSTS myLibrary.nupkg
  </code></pre>
  
  <p>This general spec, pack, push method works fine.</p>
  
  <p>It was my understanding that pushing the .nupkg file would also push up the .snupkg symbol file with it as long as it's in the same directory as per <a href="https://docs.microsoft.com/en-us/nuget/create-packages/symbol-packages-snupkg#publishing-a-symbol-package" rel="nofollow noreferrer">this</a> documentation:</p>
  
  <blockquote>
    <p>You can also push <strong>both primary and symbol packages at the same time</strong>
    using the below command. Both .nupkg and .snupkg files need to be
    present in the current folder. </p>
    
    <p><code>nuget push MyPackage.nupkg</code></p>
  </blockquote>
  
  <p>However, after installing the package, I am not able to step-into the package code.  I also don't see anything new in the package install folder.  Just the standard nupkg and the dll.  How do I push up the symbols and subsequently get them to install?</p>