Update symbol package format #2018
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hazzik
approved these changes
Feb 24, 2019
|
I have launched the release build and intend to check its artifacts before merging. |
|
The artifacts are not correct. I guess the sdk has to be updated on the build server. |
|
Closed because we can indeed already add SourceLink, and I do not think we should have two PRs for this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NHibernate goes on building symbol.nupkg since v5.0 although they are no more consumable with library built from
Sdkprojects (new .csproj format).We should switch to building snupkg.
Related: #1971. (Sourcelink cannot be added yet because it implies adding a pre-release dependency.)