Strong-name sign OmniSharp assemblies #2143
Merged
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
|
@filipw @david-driscoll please take a look. |
updated to signed dotnet.script
This was referenced May 5, 2021
|
Should I expect Omnisharp.exe to be signed at this point? I have 1.37.0 and there is no digital signature on the exe |
|
Strong name signing does not refer to that type of digital signature. And yes, Omnisharp has been shipping strongname signed binaries since 1.37.9. |
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.
In order to use dotnet/roslyn#52907, we're going to need to strong-name sign the OmniSharp assemblies. This does just that.