Skip to content

Document that TargetFramework values are aliases that drive moniker properties #53159

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.

Sign up for GitHub

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

Merged
nkolev92 merged 6 commits into from
Apr 17, 2026
Merged

Document that TargetFramework values are aliases that drive moniker properties #53159

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
5d1e9ac
Initial plan
Copilot Apr 15, 2026
64d5b38
Document TargetFramework aliasing and duplicate framework support in …
Copilot Apr 15, 2026
5e475a7
Update docs/standard/frameworks.md
nkolev92 Apr 15, 2026
a1435c2
Update docs/standard/frameworks.md
nkolev92 Apr 15, 2026
3f5fa77
Address review: fix suggestion artifact, remove multi-targeting subse…
Copilot Apr 15, 2026
3501898
Update docs/standard/frameworks.md
gewarren Apr 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 30 additions & 1 deletion docs/standard/frameworks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: Target frameworks in SDK-style projects - .NET
description: Learn about target frameworks for .NET apps and libraries.
ms.date: 11/06/2025
ms.date: 04/15/2026
ms.service: dotnet
ms.custom: updateeachrelease
ms.subservice: standard-library
Expand Down Expand Up @@ -208,6 +208,35 @@ public class MyClass
}
```

### TargetFramework values are aliases

The `TargetFramework` property value (for example, `net10.0`) is a friendly name—an alias—that the .NET SDK translates into canonical moniker properties. Specifically, the SDK sets the following properties from the `TargetFramework` value:

- `TargetFrameworkMoniker` (for example, `.NETCoreApp,Version=v10.0`)
- `TargetFrameworkIdentifier` (for example, `.NETCoreApp`)
- `TargetFrameworkVersion` (for example, `v10.0`)
- `TargetPlatformMoniker`, `TargetPlatformIdentifier`, and `TargetPlatformVersion` (when targeting a specific platform)

NuGet and the .NET SDK use these moniker properties—not the `TargetFramework` string—for package compatibility checks and build logic. This translation already happens for OS-specific TFMs. For example, `net10.0-windows` translates to `TargetFrameworkMoniker` = `.NETCoreApp,Version=v10.0` and `TargetPlatformMoniker` = `Windows,Version=7.0`.

Because the alias is just a name, the `TargetFramework` value can be any alphanumeric string, as long as the corresponding moniker properties are set correctly. The following project file uses a custom alias named `banana` and explicitly sets the moniker properties so that the project builds and restores for .NET 10.0:

```xml
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>banana</TargetFramework>
</PropertyGroup>

<PropertyGroup Condition=" '$(TargetFramework)' == 'banana' ">
<TargetFrameworkIdentifier>.NETCoreApp</TargetFrameworkIdentifier>
<TargetFrameworkVersion>v10.0</TargetFrameworkVersion>
<TargetFrameworkMoniker>.NETCoreApp,Version=v10.0</TargetFrameworkMoniker>
</PropertyGroup>
</Project>
```

For more information about these properties, see the [TargetFramework](../core/project-sdk/msbuild-props.md#targetframework) MSBuild property reference.

## Preprocessor symbols

The build system is aware of preprocessor symbols representing the target frameworks shown in the [Supported target framework versions](#supported-target-frameworks) table when you're using SDK-style projects. To convert a .NET Standard, .NET Core, or .NET 5+ TFM to a preprocessor symbol, replace dots and hyphens with an underscore, and change lowercase letters to uppercase (for example, the symbol for `netstandard2.0` is `NETSTANDARD2_0`).
Expand Down
Loading