Target Framework Moniker
lastmod 2023-04-06created 2023-04-063 edits
When you target a framework in an app or library, you specify the set of APIs you want to make available to the app or library. You specify the target framework in the project file using a TFM (target framework moniker).
Latest versions
The following table defines the most common target frameworks, how they are referenced, and which version of .NET Standard they implement. These target framework versions are the latest stable versions. Prerelease versions are not shown. A TFM (target framework moniker) is a standardized token format for specifying the target framework of a .NET app or library.
| Target framework | Latest stable version | TFM (target framework moniker) | Implemented .NET Standard version |
| .NET 7 | 7 | net7.0 | 2.1 |
| .NET 6 | 6 | net6.0 | 2.1 |
| .NET 5 | 5 | net5.0 | 2.1 |
| .NET Standard | 2.1 | netstandard2.1 | N/A |
| .NET Core | 3.1 | netcoreapp3.1 | 2.1 |
| .NET Framework | 4.8 | net48 | 2.0 |
Supported target frameworks
A target framework is typically referenced by a TFM. The following table shows the target frameworks supported by the .NET SDK and the NuGet client. Equivalents are shown within brackets. For example, win81 is an equivalent TFM to netcore451.
| Target framework | TFM |
| .NET 5+ (and .NET Core) |
|
| .NET Standard |
|
| .NET Framework |
|
| Windows Store |
|
| .NET Micro Framework |
|
| Silverlight |
|
| Windows Phone |
|
| Universal Windows Platform |
|