-
Notifications
You must be signed in to change notification settings - Fork 977
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
.NET Standard 1.x support #368
Comments
I think you mean #106? The reason for 2.x had to do with the new Streams API that we rely on (see System.IO.Stream.Close()) Why are you supporting 1.6? There are hardly any benefits support-wise. For older frameworks we support |
We are supporting 1.6 primarily for .NET Core 1.x support. We already target Okay, so maybe you can't port the latest version to .NET Standard 1.x, what about doing an update to an older version to support it? We don't need the latest features, we just need a way to support BTW - the top 2 projects on NuGet are NUnit and NewtonSoft.Json and both of them support .NET Standard 1.x, along with most of the other projects on the first page. |
I see, we have no plans to add support for 1.x unfortunately. |
I suppose an older target would also conflict with #369, unless the extra bits were conditionally included. |
Thanks for closing this. Actually, we have already dropped support for .NET Standard 1.x because it became too difficult to support. So this problem has resolved itself. |
I read #206 already, and it seems you could support .NET Standard 1.3 with no changes. Why did you only add support for .NET Standard 2.0?
We depend on this library and support .NET Standard 1.6, but had to go with an "unofficial" copy SharpZipLib.NetStandard. However, that library is not strong named and we have recently added strong naming. So, now we are stuck either releasing yet another clone, or getting you to support .NET Standard 1.x.
The text was updated successfully, but these errors were encountered: