Latest version 5.0.0 on NuGet is incompatible with full framework

migrating-ravens / RavenMigrations

A small migrations framework to help you manage your RavenDB Instance.

MIT License

52 stars 23 forks source link

Latest version 5.0.0 on NuGet is incompatible with full framework #54

Closed lahma closed 3 years ago

lahma commented 3 years ago

I couldn't find the source that corresponds the published package here, but it seems that the target has been changed from netstandard2.0 to netstandard2.1. netstandard2.1 only works with .NET Core 3.1 and thus makes this package unusable from full framework which can only handle netstandard2.0.

Could the target be changed back to nestandard2.0?

JudahGabriel commented 3 years ago

For now, I'd recommend using the previous stable version.

lahma commented 3 years ago

Is there a long term plan for versions?

JudahGabriel commented 3 years ago

Well, I had assumed most folks using this library are on .NET Core, as that is where all new development is taking place.

What's the story for .NET Standard and the .NET framework? Will there be a .NET framework that implements .NET Standard 2.1?

lahma commented 3 years ago

Unfortunately no. Netstandard2.0 is presumably last version full framework will ever support, from 4.6.1 onward I guess.

JudahGabriel commented 3 years ago

I think it's unsustainable for us, then, to continue supporting that old version of .NET Standard. I think your best bet going forward is:

In the immediate: use the previous stable RavenMigrations
In the long-term: if you anticipate active development in your project, look at migrating to .NET Core

lahma commented 3 years ago

Fair enough. I think my original expectations came from RavenDB.Client supporting .NETStandard2.0, but naturally you call the shots 🙂