Feature request: provide a strong-named build/package
First, thank you for maintaining SharpSevenZip. It is a very useful way to access the 7-Zip engine from .NET without requiring the application to invoke 7z.exe directly.
Problem
I am using SharpSevenZip from a strong-named .NET Framework 4.8 application.
The current SharpSevenZip assembly is not strong-named, which results in the following compiler warning:
warning BC41997: Referenced assembly 'SharpSevenZip, Version=2.0.111.0, Culture=neutral, PublicKeyToken=null' does not have a strong name.
This is particularly inconvenient for applications/libraries that use strong naming throughout their dependency chain.
Proposed solution
Would you consider providing a strong-named variant of the NuGet package, or otherwise making a strong-named SharpSevenZip assembly available?
For example, one possible approach could be a separate package such as:
while leaving the existing SharpSevenZip package unchanged.
Alternatively, if you consider it appropriate, the existing package could become strong-named in a future major version.
I would leave the exact packaging/signing approach to the maintainers.
Why a separate package could be useful
A separate package would preserve compatibility for existing users who currently reference the unsigned assembly, while allowing applications with strong-naming requirements to consume SharpSevenZip without having to maintain a private rebuild.
This would also avoid requiring users to manually re-sign the assembly themselves.
Environment
- .NET Framework 4.8
- VB.NET
- Strong-named application
- SharpSevenZip 2.0.111
The issue is purely related to the managed SharpSevenZip assembly; I am not requesting that the underlying native 7-Zip DLLs be strong-named.
Thank you for considering this.
Feature request: provide a strong-named build/package
First, thank you for maintaining SharpSevenZip. It is a very useful way to access the 7-Zip engine from .NET without requiring the application to invoke
7z.exedirectly.Problem
I am using SharpSevenZip from a strong-named .NET Framework 4.8 application.
The current SharpSevenZip assembly is not strong-named, which results in the following compiler warning:
This is particularly inconvenient for applications/libraries that use strong naming throughout their dependency chain.
Proposed solution
Would you consider providing a strong-named variant of the NuGet package, or otherwise making a strong-named SharpSevenZip assembly available?
For example, one possible approach could be a separate package such as:
while leaving the existing
SharpSevenZippackage unchanged.Alternatively, if you consider it appropriate, the existing package could become strong-named in a future major version.
I would leave the exact packaging/signing approach to the maintainers.
Why a separate package could be useful
A separate package would preserve compatibility for existing users who currently reference the unsigned assembly, while allowing applications with strong-naming requirements to consume SharpSevenZip without having to maintain a private rebuild.
This would also avoid requiring users to manually re-sign the assembly themselves.
Environment
The issue is purely related to the managed
SharpSevenZipassembly; I am not requesting that the underlying native 7-Zip DLLs be strong-named.Thank you for considering this.