Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Sign the assembly with a strong name key
See original GitHub issueIs your feature request related to a problem? Please describe. If I reference this assembly from an assembly that is signed with strong name key file, I receive the following warning from the compiler:
CS8002: Referenced assembly 'Blazored.LocalStorage, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' does not have a strong name.
Describe the solution you’d like The assembly needs to be signed with a strong name key file (see the Signing tab in the Project Properties dialog in Visual Studio) to resolve this warning for any signed projects that reference this library.
Describe alternatives you’ve considered Unsigning my assembly. Not ideal, as it is best practice to sign .Net assemblies (see https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/strong-naming)
Additional context I am happy to create a pull request with this change (it is a straightforward change).
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@pmachapman I’ve asked where Egil is on this. If he isn’t happy about signing bUnit, then I don’t think there is much point in signing Blazored. We’ll have to see what he comes back with.
Yes I get the warning for the v4 branch - didn’t think to test the v4 branch - d’oh!
Looks like it is an issue they are aware of since Feb: https://github.com/egil/bUnit/issues/316