You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We've been using prior versions of SharpZipLib with .NET Framework and once upgrading, we are running into issues at compile time referencing .NET Standard 2.0. For various reasons, we're unable to upgrade our .NET Framework version up to 4.7.2+. Per Microsoft:
While NuGet considers .NET Framework 4.6.1 as supporting .NET Standard 1.5 through 2.0, there are several issues with consuming .NET Standard libraries that were built for those versions from .NET Framework 4.6.1 projects. For .NET Framework projects that need to use such libraries, we recommend that you upgrade the project to target .NET Framework 4.7.2 or higher. (https://learn.microsoft.com/en-us/dotnet/standard/net-standard?tabs=net-standard-2-0)
Describe the solution you'd like
Add net461 to this line. We are not sure if there's more that would need to happen as we are not familiar with this code base.
Describe alternatives you've considered
The only other solution that we would be able to do would be to compile this ourselves internally.
Tags
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We've been using prior versions of SharpZipLib with .NET Framework and once upgrading, we are running into issues at compile time referencing .NET Standard 2.0. For various reasons, we're unable to upgrade our .NET Framework version up to 4.7.2+. Per Microsoft:
Describe the solution you'd like
Add net461 to this line. We are not sure if there's more that would need to happen as we are not familiar with this code base.
Describe alternatives you've considered
The only other solution that we would be able to do would be to compile this ourselves internally.
Tags
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: