Stuck on an issue?

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.

[Question]: Any plans for strongly named assembly in NuGet?

See original GitHub issue

Hi team,

I used the older framework which is now deprecated, I tried upgrading to this version, however one of my project is signed. I cannot remove the signing and because of that, I am getting the following error when I run the project:

'Could not load file or assembly 'Krypton.Toolkit, Version=5.550.2011.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044)'

I also tried to uncheck the singing and check if its working, it works however, the project uses isolated storage, when we uncheck the signing, the isolated storage gets cleared which is not the correct way to handle it,

Can you please provide us with a strongly named assembly in nuget so that the people who were using it wont face this issue too?

Thanks.

Issue Analytics

State:
Created 3 years ago
Comments:11 (5 by maintainers)

Top GitHub Comments

1reaction

Wagnerpcommented, Nov 10, 2020

Hi @pankaj-nikam

No problem, good to see that it’s now working!

1reaction

pankaj-nikamcommented, Nov 10, 2020

Hi @Wagnerp , Yes, installing the full version enabled the designer. Thank you so much for help and maintaining this project for the future version of .NET too 👍

Top Results From Across the Web

Assembly from nuget has strong name but cause build ...

I had similar issue, after publishing and trying to build a newer version with VS2017. I switched, in the properties->publish -> application ...

Strongly Named Assemblies in Nuget

The problem is that strongly named assemblies depend upon asymmetric encryption. The assembly name, version, culture, and files are signed, and ...

Strong naming and .NET libraries

When an assembly is strong-named, it creates a unique identity based on the name and assembly version number, and it can help prevent...

Strongly Name the assemblies · Issue #216 · restsharp ...

The solution is simple: understand the limitations of strong names and develop a breaking changes policy and NuGet package specification which ...

NET Assembly Strong-Name Signer

Supports strong-name signing assemblies built in v1. · Accessible via GUI, command-line or programmatic API. · Round-trips assembly attributes (32-bit preferred, ...