-
Notifications
You must be signed in to change notification settings - Fork 444
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
Support sibling snupkg file #926
Support sibling snupkg file #926
Conversation
c3814dd
to
8036cb9
Compare
8036cb9
to
34e5460
Compare
I’ll test and merge tomorrow, thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One final thing and then it'll be ready.
requireExternal = true; | ||
if (response.IsSuccessStatusCode) // we'll get a 404 if none | ||
{ | ||
requireExternal = true; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to set requireExternal
to true for the local snupkg
case as well. This is because it'll ultimately require a symbol server to work.
Oh, one other thought -- as long as we're checking for |
f9ea300
to
b500bea
Compare
{ | ||
ReadSnupkgFile(snupkgFilePath); | ||
} | ||
if (File.Exists(symbolsFilePath)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be else if
When opening a nupkg file from disk, if its symbols are in a .snupkg or .symbols.snupkg file next to it, it would be flagged as having no symbols. This commit tests for such a file, using it if possible, before returning to the prior behaviour of checking nuget.org for packages identified as coming from there.
b500bea
to
263c62c
Compare
Fixes #925.
When opening a
nupkg
file from disk, if its symbols are in asnupkg
file next to it, it would be flagged as having no symbols. This commit tests for such a file, using it if possible, before returning to the prior behaviour of checking nuget.org for packages identified as coming from there.