EOL.Wiki EOL.Wiki
← ← Back to all products

.NET

Active
Runtimes & JDKs Latest Version: 10.0.3 Latest Release: Feb 10, 2026

.NET is a free, cross-platform, open-source developer platform by Microsoft for building modern applications.

Versions

13

Latest Version

10.0.3

Active Support

3

EOL

10

Lifecycle Timeline

Today
10
10
9
9
8
8
7
7
6
6
5
5
3.1
3.1
3.0
3.0
2.2
2.2
2.1
2.1
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
10Nov 11, 2025-Nov 14, 202810.0.3
Yes
Active
9Nov 12, 2024-Nov 10, 20269.0.13No
Active
8Nov 14, 2023-Nov 10, 20268.0.24
Yes
Active
7Nov 8, 2022-May 14, 20247.0.20No
EOL
6Nov 8, 2021-Nov 12, 20246.0.36
Yes
EOL
5Nov 10, 2020-May 10, 20225.0.17No
EOL
3.1Dec 3, 2019-Dec 13, 20223.1.32
Yes
EOL
3.0Sep 23, 2019-Mar 3, 20203.0.3No
EOL
2.2Dec 4, 2018-Dec 23, 20192.2.8No
EOL
2.1May 30, 2018-Aug 21, 20212.1.30
Yes
EOL
2.0Aug 14, 2017-Oct 1, 20182.0.9No
EOL
1.1Nov 16, 2016-Jun 27, 20191.1.13No
EOL
1.0Jun 27, 2016-Jun 27, 20191.0.16No
EOL

Frequently Asked Questions

Which versions of .NET have reached end of life?
The following .NET versions have reached end of life and no longer receive security updates: 7, 6, 5, 3.1, 3.0, 2.2, 2.1, 2.0 (and 2 more). It is recommended to upgrade to a supported version.
Is it safe to continue using .NET 7?
.NET 7 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of .NET?
The latest version of .NET is 10.0.3, released in the 10 release cycle.
How many versions of .NET are currently supported?
.NET currently has 3 actively supported version(s): 10, 9, 8.
When does .NET 10 reach end of life?
.NET 10 is scheduled to reach end of life on Nov 14, 2028.
What should I do when .NET reaches end of life?
When a .NET version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.