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

Why no longer support for netstandard and previous .net versions? #363

Open
msmolka opened this issue Feb 10, 2023 · 5 comments
Open

Why no longer support for netstandard and previous .net versions? #363

msmolka opened this issue Feb 10, 2023 · 5 comments

Comments

@msmolka
Copy link

msmolka commented Feb 10, 2023

Latest lib supports only net7, I wonder why

@leonid-lm
Copy link

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.

@ardalis
Copy link
Owner

ardalis commented Apr 6, 2023

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.

@jafin
Copy link
Contributor

jafin commented Jun 12, 2023

@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)

@alvipeo
Copy link

alvipeo commented Jul 8, 2023

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 Update-Package. Now I need to go and upgrade the packages one by one! :(

@GrantByrn3
Copy link

I would also like to see support for .net standard. Unfortunately that's a blocker for me to using this project

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

Successfully merging a pull request may close this issue.

6 participants