Skip to content
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

2.0.0 have not been published to Nuget #7

Open
ied206 opened this issue Jan 20, 2018 · 6 comments
Open

2.0.0 have not been published to Nuget #7

ied206 opened this issue Jan 20, 2018 · 6 comments

Comments

@ied206
Copy link

ied206 commented Jan 20, 2018

In nuget 1.2.2 is the lastest version of XZ.NET.
Is there any reason prevented upload of 2.0.0?

Many improvements like AnyCPU build were achieved in 2.0.0, so it would be better to let developers use lastest version of XZ.NET via nuget.

@ied206 ied206 changed the title 2.0.0 had not been published to Nuget 2.0.0 have not been published to Nuget Jan 20, 2018
@RomanBelkov
Copy link
Owner

Hello @ied206,

I have a very small amount of spare time since I can't remember when. Thanks for your notice, I will definitely push the 2.0.0 ASAP to nuget.

@ied206
Copy link
Author

ied206 commented Feb 25, 2018

Does current XZ.Net 2.0 version has issues? It have been still not updated on nuget.

@ScottDennison
Copy link

ScottDennison commented Nov 9, 2018

The development team at Costcutter has also just been bitten by 2.0 not being available on NuGet.
Please could this be published?

@RomanBelkov
Copy link
Owner

Hello all,

I am deeply sorry for such incredible delay with publishing this on NuGet.
The package should be shortly available from https://www.nuget.org/packages/XZ.NET/2.0.0.

Please let me know if it does not work for you.

@bastianeicher
Copy link

There seem to be separate NuGet packages for x86 and x64. However, both contain a .NET library which, looking at the source, should be Any CPU, and both the 32bit and 64bit version of the native library. Couldn't this be turned into a single NuGet package?

Perhaps you could use #10 to build a new release?

@ScottDennison
Copy link

Having tried to incorproate the 2.0 nuget into the project at costcutter, I ran into the same issue as @bastianeicher.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants