-
-
Notifications
You must be signed in to change notification settings - Fork 172
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
Why no longer support for netstandard and previous .net versions? #363
Comments
From my point of view, it is a really strange decision to get bounded to .Net 7.0 completely forgetting about .netstandard 2.1. If this lib still could be positioned like a "core" library it must support .netstandard 2.1. |
I should probably add netstandard 2.1 support back in. I was thinking when I removed it that most folks were on the net6 or net7 LTS/current versions and I neglected to consider all the teams who aren't there yet. |
@ardalis It would be great to support the latest LTS Version of .NET Core. (currently .net6) Some shops build on LTS, not the latest feature release (due to lagging release cycle) , so it is beneficial to have that targeting if possible. I did up a PR for net6/netstandard 2.1 (I'm neither here nor there on netstandard, but as you mentioned it above I included it) |
It's still not in nuget :( I've been using this package for years now (thanks!). But suddenly I can't upgrade any package in my .netstandard 2.1 projects with |
I would also like to see support for .net standard. Unfortunately that's a blocker for me to using this project |
Latest lib supports only net7, I wonder why
The text was updated successfully, but these errors were encountered: