-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Strong name signing #47
Comments
Hi, |
As far as I understand the situation, just adding strong naming to the library may break the dependency resolution of any application that is currently not using strong naming. Therefore strong naming of NanoXLSX would enforce using strong naming of the applications that are using NanoXLSX. |
After some tries and further investigation, I came to terms, not to use strong naming at the moment.
Sorry about that. My suggestion is to create a fork of the library and to enable strong naming in your own environment. Then you have full control over your code. Usually, changes in this library should be easy to adapt, since no external dependencies are involved. I can of course try to help if upstream changes are making problem to be implemented in the fork. |
We are trying to use NanoXLSX within a website (asp.net) application. The library won't load as it is not strong named.
https://learn.microsoft.com/en-us/dotnet/standard/assembly/sign-strong-name
Can you add a key and enable strong naming please?
The text was updated successfully, but these errors were encountered: