Skip to content

Correct TargetFramework precedence documentation - #55873

Open
gewarren with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-targetframework-precedence-note
Open

Correct TargetFramework precedence documentation#55873
gewarren with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-targetframework-precedence-note

Conversation

Copilot AI commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

The documentation reverses the precedence of TargetFramework and TargetFrameworks. A non-empty TargetFramework takes precedence and produces a single-target build.

  • Documentation
    • Corrects the precedence note under TargetFrameworks.
    • Clarifies that TargetFrameworks is ignored when TargetFramework is specified.

Internal previews

File Preview link
docs/core/project-sdk/msbuild-props.md Learn preview

Build report

Copilot AI lite review requested due to automatic review settings September 2, 2026 18:48

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review any files in this pull request.


💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

Co-authored-by: gewarren <24882762+gewarren@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix msbuild props target framework precedence note Correct TargetFramework precedence documentation Sep 2, 2026
Copilot AI requested a review from gewarren September 2, 2026 18:50
@gewarren
gewarren marked this pull request as ready for review September 3, 2026 23:23
@gewarren
gewarren requested a review from a team as a code owner September 3, 2026 23:23
@gewarren
gewarren requested a balanced review from Copilot September 3, 2026 23:25

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

The precedence note must explicitly require TargetFramework to be non-empty.

Review details

Suppressed comments (1)

docs/core/project-sdk/msbuild-props.md:147

  • This overstates the precedence rule: the SDK condition cited in #55612 requires TargetFramework to be non-empty. If the property is present but evaluates to an empty string, a non-empty TargetFrameworks still enables cross-targeting. State the non-empty requirement so the note matches the documented SDK behavior.
> If `TargetFramework` (singular) is specified, `TargetFrameworks` (plural) is ignored, and the project builds as a single-target project.
  • Files reviewed: 1/1 changed files
  • Comments generated: 0 new
  • Review effort level: Balanced

@BillWagner BillWagner left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This LGTM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

msbuild-props: TargetFramework/TargetFrameworks precedence note is backwards

4 participants