This repository has been archived by the owner on Sep 22, 2021. It is now read-only.
Added nuget install script that excludes us from Strong Name verification #39
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
…tion [ci skip] because all of this only matters on master. Someone please test this on Windows.
Did not work for me, is there a Travis run of this anywhere? |
|
No, because this cannot be tested with Travis - Travis is linux-based, and the problem is windows-only. I currently don't have a Windows-installation to test it. If you want to resolve the problem manually run After a restart of Visual Studio it should work. This is only a problem in the prerelease-package. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Apparently .NET straight up rejects delay signed assemblies even in full trust environments unless you exclude them manually using the Strong Name tool.
Todo: