You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add new SDK versions and clean up out of support versions (#44418)
* Add new SDK versions and clean up out of support versions
Added 9.0.2xx and 9.0.3xx bands
Added 10.0.100 preview 1
Moved the targeting information to the targeting section
Removed some unnecessary notes
Remove the out of support versions from the target table
* Apply suggestions from code review
Co-authored-by: Genevieve Warren <[email protected]>
---------
Co-authored-by: Genevieve Warren <[email protected]>
| 8.0.1xx | 17.8 | Nov '23 | Nov '25<sup>1</sup> |
59
-
| 8.0.2xx | 17.9<sup>3</sup>| Feb '24 | May '24<sup>3</sup>|
59
+
| 8.0.2xx | 17.9 | Feb '24 | May '24|
60
60
| 8.0.3xx | 17.10 | May '24 | TBD |
61
61
| 8.0.4xx | 17.11 | Aug '24 | Nov '25<sup>2</sup> |
62
-
| 9.0.1xx | 17.12 | Nov '24 | May '26<sup>1</sup> |
62
+
| 9.0.1xx | 17.12 | Nov '24 | May '26 |
63
+
| 9.0.2xx | 17.13 | Feb '25 | May '26 |
64
+
| 9.0.3xx | 17.14 | May '25 | May '26 |
63
65
64
66
> [!NOTE]
65
-
> Targeting `net6.0` is officially supported in Visual Studio 17.0+ only.
66
-
> Targeting `net7.0` is officially supported in Visual Studio 17.4+ only.
67
-
> Targeting `net8.0` is officially supported in Visual Studio 17.8+ only.
68
-
>
69
67
> <sup>1</sup> .1xx .NET SDK feature bands are supported throughout the lifecycle of major .NET versions. During the extended support period, support is limited to security fixes and minimal high-priority non-security fixes for Linux only. To learn more about the reasoning for this extended support, see [Source-build support](https://github.com/dotnet/source-build#support).
70
68
>
71
69
> <sup>2</sup> .4xx .NET SDK feature bands are supported for the life of the matching runtime as stand-alone installs.
72
70
>
73
-
> <sup>3</sup> 8.0.200 requires a newer Visual Studio version. For more information, see the [support rules](#targeting-and-support-rules).
74
-
>
75
71
> [Visual Studio 2019 Lifecycle](/lifecycle/products/visual-studio-2019)
76
72
>
77
73
> [Visual Studio 2022 Lifecycle](/lifecycle/products/visual-studio-2022)
@@ -86,23 +82,20 @@ A the following policy dictates which versions of MSBuild and Visual Studio a gi
86
82
87
83
| SDK | Visual Studio version<br/>the SDK ships with | Minimum Visual Studio version | Max TargetFramework in<br/>minimum Visual Studio version | Max TargetFramework in `dotnet`|
> The table depicts how these versioning rules are applied, starting with .NET SDK 7.0.100 and .NET SDK 6.0.300. It also depicts how the policy would have applied to previously shipped versions of the .NET SDK, had it been in place then. However, the requirements for previous versions of the SDK don't change—that is, the minimum required version of Visual Studio for .NET SDK 6.0.100 or 6.0.200 remains 16.10.
104
-
105
-
> <sup>1</sup> A breaking change in 7.0.300 for Blazor and Razor development requires Visual Studio version 17.6 or newer. For more information, see [dotnet/razor issue 8718](https://github.com/dotnet/razor/issues/8718).
95
+
>
96
+
> Targeting `net8.0` is officially supported in Visual Studio 17.8+ only.
97
+
>
98
+
> Targeting `net9.0` is officially supported in Visual Studio 17.12+ only.
106
99
107
100
To ensure consistent tooling, you should use `dotnet build` rather than `msbuild` to build your application when possible.
108
101
@@ -112,16 +105,10 @@ Major versions of the .NET SDK are typically released within a few days of a Vis
0 commit comments