Older references and paket - Is this project abanonded now?

[gdau]

Sorry if this is the wrong place to ask, but is this project still being maintained? It's enforcing older versions of shared components (like JSON.NET < 10) which is causing conflicts with other libraries.

I would love to see this project continue as I rely on it for integration with rackspace but will branch it and replace "paket" with just regular nuget packages if this is no longer going to receive any updates.

paket refuses to build this project on my machine because of xunit and other conflicts now - perhaps I'm not understanding what something like paket brings to the table for this project. I replaced the paket references with nuget references for the latest JSON.NET, flurl and marvin patch depdendencies and only required a single tweak to the code to get it working so not sure why such old versions are pinned (if this is in the documentation, I apologise - it wasn't obvious when I looked for it).

Thank you. This project has been a lifesaver.

[nsp37]

It would be awesome if you put up a branch / fork using NuGet and these newer versions. We would totally use.

[dwalleck]

Sorry to hear about the pains you've had. This project was in-between maintainers for the last 5-6 months, but I've taken the plunge to step in and help get things moving again. If migrating away from using Paket is something the community is behind, I'd be more than glad to make that happen. Using Paket may have made more sense at the time, but NuGet has come a long way in the past few years and is the preferred tooling for most C#/.NET projects I've seen.

[tommymonk]

That sounds good to me !

[johnmasson]

What's the current status of this? The max version of JSON.NET is blocking an upgrade of other packages for us: I can see that it was apparently removed in the .nuspec, but there doesn't seem to be an updated NuGet package available (latest is still 1.7.7 which still has the max version constraint)?

[JRichmond27]

It's now April 2018, and the NuGet package still restricts to JSON.Net < 10.0.0. Can we please get an updated package?

[dwalleck]

I was having some issues with the Paket build which I've thankfully found some help with. I've created an RC package (https://www.nuget.org/packages/openstack.net/1.7.8-rc) that should resolve this issue. If you have a chance, try it out and let me know if that solves your problem.

[JRichmond27]

I'm trying to update to openstack.net 1.7.8, but now the problem is that it's requiring Flurl.Signed between 1.0.0 and 1.1.0, but the lowest available version of Flurl.Signed is 2.7.1. Anyone know where I can find a lower version?

EDIT: I was able to get the deprecated versions of Flurl.Signed and Flurl.Http.Signed from here:
https://www.nuget.org/packages/Flurl.Signed/1.0.10
https://www.nuget.org/packages/Flurl.http.Signed/0.7.0

Before upgrading to openstack.net 1.7.8, I had been using Flurl.Signed 2.7.1 with no issues. Any chance we can get updated dependencies for these?

[BogusException]

FYI:

PM> Update-Package Flurl.Signed

Attempting to gather dependency information for multiple packages with respect to project 'SharedProject', targeting '.NETFramework,Version=v4.6.2'
Gathering dependency information took 12.86 sec
Attempting to resolve dependencies for multiple packages.
Update-Package : Unable to resolve dependencies. 'Flurl.Signed 2.8.0' is not compatible with 'openstack.net 1.7.8 constraint: Flurl.Signed (>= 1.0.0 && < 1.1.0)'.