Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Add support for .NET Framework 4.6.1 to target frameworks. #863

Open
calvinvoss opened this issue May 1, 2024 · 0 comments · May be fixed by #872
Open

Add support for .NET Framework 4.6.1 to target frameworks. #863

calvinvoss opened this issue May 1, 2024 · 0 comments · May be fixed by #872
Labels
enhancement Feature request or other improvements of existing functionality *no response*

Comments

@calvinvoss
Copy link

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

@calvinvoss calvinvoss added the enhancement Feature request or other improvements of existing functionality label May 1, 2024
@icsharpcode icsharpcode deleted a comment from SourceproStudio May 2, 2024
@lahma lahma linked a pull request Jul 18, 2024 that will close this issue
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement Feature request or other improvements of existing functionality *no response*
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant