Skip to content

Commit 72da6b3

Browse files
authored
Merge pull request #1421 from nunit/CharliePoole-patch-1
Create platform-support.md
2 parents f032bb5 + 3b94aec commit 72da6b3

File tree

1 file changed

+49
-0
lines changed

1 file changed

+49
-0
lines changed

platform-support.md

+49
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
# Platform Support Lifecycle
2+
3+
"Platform Support" for this project includes three somewhat different things:
4+
1. Test assembly target platforms, that is, the target platforms for which tests may be written.
5+
2. The target platforms under which those tests will actually run, which is equivalent to the list of agents we provide.
6+
3. The minimum platforms required to execute the runner and engine themselves, without regard to the tests being run.
7+
8+
## Test Assembly Target Runtimes
9+
10+
We currently support execution of tests written to target any version of the .NET Framework >= 2.0 and any version
11+
of .NET Core >= 3.1, including .NET 5.0 and higher. We will continue to support tests targeting runtimes which are
12+
out of support from Microsoft's perspective, so long as we are able to do so without significant additional effort
13+
and without security risk. If no agent is available for a runtime, the tests will be run on the closest higher
14+
runtime available.
15+
16+
## Agents Provided
17+
18+
We currently supply a fairly large selection of agents with the console runner:
19+
* .NET Framework 2.0
20+
* .NET Framework 4.6.2
21+
* ,NET Core 3.1
22+
* .NET 5.0
23+
* .NET 6.0
24+
* .NET 7.0
25+
* .NET 8.0 (coming in version 3.18.0)
26+
27+
As a general policy, we will continue to provide agents for any Microsoft runtime for at least six months after its
28+
official end of life. This is intended to support continued testing of legacy applications while users are in the
29+
process of upgrade. However, agents for runtimes which have been declared a security risk may be removed immediately.
30+
31+
Based on that policy and the planned end-of-life dates for runtimes, we expect to retire agents on or after the
32+
dates listed in the following table.
33+
34+
| Runtime | Microsoft<br>End of Support | Agent Retirement | Notes |
35+
| -------------------- | --------------- | --------------------- | --- |
36+
| .NET Framework 2.0 | July, 2011 | July, 2024 | Will be removed in version 3.18.0
37+
| .NET Framework 4.6.2 | January, 2027 | after July, 2027 | May be upgraded to 4.8.1 before retirement date |
38+
| .NET Core 3.1 | December, 2022 | after December, 2024 |
39+
| .NET 5.0 | May, 2022 | July, 2024 | Will be removed in version 3.18.0
40+
| .NET 6.0 | November, 2024 | after May, 2025 |
41+
| .NET 7.0 | May, 2024 | after November, 2024 |
42+
| .NET 8.0 | November, 2027 | after May, 2027 |
43+
44+
## Required Runtimes
45+
46+
The console runner and engine target .NET Framework 4.6.2, so that runtime or greater is required to execute any tests at all
47+
without loss of features. In individual cases, it may be possible to run using a lesser version of .NET 4.x. It's possible
48+
that we may require a higher level of the framework in a future 3.x release.
49+

0 commit comments

Comments
 (0)