'How to make my nuget package able to "step in"?
Im releasing a nuget package and I'd like that whoever is using it could step into it as if it was his own code.
In order to do that, in the RELEASE configuration (which is the one I use for distribution), I try set the "Debug Information:" to Embedded and Portable but none did the trick! When I install the package, the pub files are never there...
What am I doing wrong?
Solution 1:[1]
The answer from memory is:
- Visual Studio has a config setting for a Symbol Server which must point to source code with the same pdb file produced with the compile used for creating the nuget package.
- There are different ways to host the symbol server. The easiest is to simply clone the repo from same version the nuget package was created from. Compile that code to generate the pdb. Then point the symbol server config to the bin folder containing the pdb of that compile.
- Reboot visual studio.
Now try to single step into that code.
The real symbol server is produced as a website. Plenty of doc. On how to do that.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 |
