Document that TargetFramework values are aliases that drive moniker properties#53159
Open
Document that TargetFramework values are aliases that drive moniker properties#53159
Conversation
…frameworks.md Agent-Logs-Url: https://github.com/dotnet/docs/sessions/7aa809ad-c4fa-4344-a7a2-ec9a92e58ce7 Co-authored-by: nkolev92 <2878341+nkolev92@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Document TargetFramework values as aliases for TargetFrameworkMoniker and TargetPlatformMoniker
Document that TargetFramework values are aliases that drive moniker properties
Apr 15, 2026
nkolev92
reviewed
Apr 15, 2026
…ction Agent-Logs-Url: https://github.com/dotnet/docs/sessions/b7935477-6fe7-4105-9ef9-088e52d55c23 Co-authored-by: nkolev92 <2878341+nkolev92@users.noreply.github.com>
nkolev92
approved these changes
Apr 15, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Adds documentation to clarify that TargetFramework values (TFMs) are aliases that the .NET SDK translates into canonical moniker properties used by the build and restore pipeline.
Changes:
- Updates
ms.dateto 04/15/2026. - Adds a new subsection explaining
TargetFrameworkalias translation intoTargetFrameworkMoniker,TargetFrameworkIdentifier,TargetFrameworkVersion, andTargetPlatform*properties. - Adds a custom alias (
banana) example that explicitly sets moniker properties.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
gewarren
approved these changes
Apr 15, 2026
javanio627-bot
approved these changes
Apr 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Target frameworks in SDK-style projects page explains TFMs but doesn't explain the underlying mechanism:
TargetFrameworkis always an alias translated into canonicalTargetFrameworkMonikerandTargetPlatformMonikerproperties.Adds a new subsection under "How to specify a target framework" in
docs/standard/frameworks.md:TargetFramework→TargetFrameworkMoniker,TargetFrameworkIdentifier,TargetFrameworkVersion, andTargetPlatform*properties. Includes the custom alias example (banana) per issue discussion, demonstrating that theTargetFrameworkvalue can be any alphanumeric string as long as the moniker properties are set correctly.Heading name aligns with the corresponding NuGet docs section to support cross-linking between the two doc sets. Complements the already-merged PR #52883 which added equivalent notes to
msbuild-props.md.Internal previews