search

haf / DotNetZip.Semverd

Please use System.IO.Compression! A fork of the DotNetZip project without signing with a solution that compiles cleanly. This project aims to follow semver to avoid versioning conflicts. DotNetZip is a FAST, FREE class library and toolset for manipulating zip files. Use VB, C# or any .NET language to easily create, extract, or update zip files.
Other
545 stars 218 forks source link

Support for .NET 6.0 #245

Open mattmckinstry opened 2 years ago

mattmckinstry commented 2 years ago

Currently the dependencies are

System.Security.Permissions (>= 5.0.0 && < 6.0.0) System.Text.Encoding.CodePages (>= 5.0.0 && < 6.0.0)

which is preventing us upgrading to .NET 6.0

maxle5 commented 2 years ago

We are running into the same issue

ladeak commented 2 years ago

@lahma what is the reason for having the upper restrictions here? https://github.com/haf/DotNetZip.Semverd/blob/e487179b33a9a0f2631eed5fb04d2c952ea5377a/paket.lock#L13

lahma commented 2 years ago

Really hard to remember the specifics, but I guess I lost the battle against the infra: https://github.com/haf/DotNetZip.Semverd/pull/214#issuecomment-726134309

JensNordenbro commented 2 years ago

Please fix!

cbersch commented 2 years ago

Really hard to remember the specifics, but I guess I lost the battle against the infra: #214 (comment)

I also tried to build the packages with an open dependency >= 5.0.0, but it seemed to me, that Paket simply doesn't support this. Finally, I also gave up against paket and rake, like @lahma.

MarcusJohnson commented 2 years ago

Any update on this?

ladeak commented 2 years ago

Any update on this?

I believe this is up for the community as the project is looking for a maintainer based on the Readme.

gokhanabatay commented 2 years ago

Any update on this?

lahma commented 2 years ago

While a terrible hack, I was able to force package dependencies to be of lower version and without upper bound:

https://github.com/haf/DotNetZip.Semverd/pull/247

lahma commented 2 years ago

@mattmckinstry can you test the latest NuGet release and possibly close this issue if works as expected?