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

Drop Support for Older .NET Versions #68

Closed
WalkerCodeRanger opened this issue Feb 13, 2022 · 2 comments
Closed

Drop Support for Older .NET Versions #68

WalkerCodeRanger opened this issue Feb 13, 2022 · 2 comments

Comments

@WalkerCodeRanger
Copy link
Owner

As of Semver v2.1.0, it will ship with DLLs targeting .NET 4.5.2, .NET Standard 1.1, and .NET Standard 2.0. However, this includes support for versions with are no longer supported by Microsoft. At some point, it is likely to become a problem to support those versions. This also limits which version of the C# language we can use. There may be features in newer versions of C# that would be beneficial to use. When the next major release occurs, we should drop support for some frameworks. We will have to decide at that point which ones it makes sense to drop support for.

MS Supported Version

From what I can tell, .NET Standard doesn't have a separate support lifecycle from the individual frameworks they support. However, MS is already saying that it is "recommend you target .NET Standard 2.0, unless you need to support an earlier version."

For reference, the old .NET standard support chart which is easier to read is reproduced here. Also, here is an article on Demystifying Microsoft .NET Long-term Support (LTS).

@WalkerCodeRanger
Copy link
Owner Author

Looking at the .NET Standard supported plaforms it looks like .NET Standard 2.0 is supported on all versions that still have suport. It appears Xamerin drops support for old versions very quickly. I was unable to find anything on Mono versions long term support.

@WalkerCodeRanger
Copy link
Owner Author

Support for target frameworks before .NET Standard 2.0 has been dropped. The reasons for targeting .NET Standard 2.0 & 2.1 and .NET 5 have been documented in FRAMEWORK_SUPPORT.md.

Thus, this has been fixed on master and will be included in v3.0.0

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

No branches or pull requests

1 participant