-
Notifications
You must be signed in to change notification settings - Fork 8
Debug into package sources #14
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
Comments
The v0.8.0 that is currently published definitely has the changes from your PR. The CI is broken and I should fix it, but I've manually published it. Not sure what's wrong with the step into source feature, was there something special to do during build? |
In project settings for Mos.xApi, I checked "Generate NuGet package on build". This produces two files: Mos.xApi.0.8.0.nupkg and Mos.xApi.0.8.0.snupkg. Then I created a console app and pointed my VS package source to the output directory. This enabled me to step into source from the console project. I think you need to upload both files. It's a bit outdated, but maybe this helps. |
Ah, yes I remember now, I had an error when trying to upload the snupkg, it failed with a not supported error. I'm try again with the next version. |
It took quite some effort, but I got it working nicely in another project. See json-api-dotnet/JsonApiDotNetCore#703 for reference. |
Tried to install v0.8.0, hoping to be able to step into sources (see #13). But it does not seem to work. Is this a bug, or does the latest release not include the bits from this PR?
The text was updated successfully, but these errors were encountered: