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.
Package does not have a strong name
See original GitHub issueDescribe the bug
I am unable to reference the LdapForNet package in an application that is strongly signed.
CSC : error CS8002: Referenced assembly 'LdapForNet, Version=2.7.10.0, Culture=neutral, PublicKeyToken=null' does not have a strong name.
To Reproduce Reference this package in a project that uses strong name signing. You cannot reference unsigned assembly from a signed assembly.
Expected behavior The package should be strongly signed.
Desktop (please complete the following information):
- OS: Windows, Linux, and FreeBSD
- Library version 2.7.10
- .NET Core 3.1
Additional information
I am currently using the following package as a workaround:
<PackageReference Include="Brutal.Dev.StrongNameSigner" Version="2.7.1" />
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 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
Also having an issue, can’t use the package without it. Can I make a PR to fix? The current guidelines suggest they key should just be in the repository, so should be easy 🙂
@flamencist any chance of having @jepperc PR #131 merged?