-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Visual studio 2019 can not load local pdb file extracted from snupkg #9302
Comments
Please uncheck |
yes, it's unchecked
I did all required options including in the symbol page. I added the path to my extracted pdb file from snupkg:
When opening the Modules window, i find a message:
Then i clicked "Symbol load information..", i find the path that i entered above show the message:
So, why it does not match image although my workaround solution in my post is working. The pdb match the same dll extracted from both snupkg and nupkg packages. It seems that some match logic is tested by VS for snupkg. Note: It was working the the legacy pdb |
I resolved the issue. The package is generated in CI appveyor for both windows and ubuntu 18.04. when I used snupkg of ubuntu image, VS 2019 load the symbol file correctly. Thanks for help. |
Environment:
Visual studio 2019 v16.4.2
console project in net461
using nuget from CI appveyor server loaded locally to my machine.
I try to debug a console project using snupkg package locally in my machine for debugging locally.
reference the package
Appveyor don't support loading snupkg, so I downloaded the corresponding snupkg package from CI Appveyor server to my machine from the artifact for test. (it's not published yet to nuget gallery)
I unzipped the snupkg file (it's zip file) to c:\folder1.
I add the path in debug options of VS:
options->debug->symbols-> c:\folder1\lib\net461\mypakag.pdb
Visual studio 2019 v16.4.2 can not recognize the symbol pdb file and fire a message:
Why Visual studio can not load the pdb file of the snupkg package? What I missed to do?
Note: I used the same procedures before with the legacy pdb
.symbol.nupkg
and it was working.This issue is different than #8809
workaround solution
Unzip both nupkg and snupkg and add pdb which is extracted from snupk in the same folder of dll then reference the the dll file in the project.
In that case VS auto load the pdb.
The text was updated successfully, but these errors were encountered: