-
-
Notifications
You must be signed in to change notification settings - Fork 447
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
Ship PDB files with Nuget package #617
Comments
See #501, I'll try to work on it this week |
Nice, SourceLink would also solve the problem, thanks for the good work! |
Is there anything planned for this? It seems like with the latest version I am not able to load the symbols in the module view during debugging. |
Source link is added #626 |
@rasmus Have you published the symbol package on NuGet? |
@DavidRouyer yes, the changes went out in release v0.70.3824 that went on NuGet org the 2019-04-11 |
But we could add the PDB files as well |
Trying it out in #638 |
@rasmus You merged the changes but you have to publish the symbols package ( On your package page https://www.nuget.org/packages/EventFlow |
Yes, the issue are the AppVeyor built-in support for uploading NuGet packages that EventFlow uses: The packages aren't picked up. I'll see if can upload them manually after the release completes until it gets fixed. Adding the files to the GitHub release here #639. But, I hope they fix it as I dislike downloading release packages to my personal desktop. If they don't it will need to be built manually. |
May have found a simple workaround |
The source link integration is broken. I opened #644 to reflect it. Closing this issue as the original idea is implemented (although broken). |
The PDB files will be in the normal package and in the snupkg as well after #645 is done |
Released in v0.72.3914 along with corrected source link support. Remember to disable "just my code" |
Would be nice to have the PDB files shipped with the nuget package to help with debugging.
For reference: aspnet/Universe#131 (comment)
The text was updated successfully, but these errors were encountered: