Fix TargetFrameworks documentation - correct precedence behavior

[Copilot]

The documentation incorrectly stated that TargetFrameworks (plural) is ignored when TargetFramework (singular) is specified. The actual behavior is the opposite.

Changes

• Updated the Note in the TargetFrameworks section to correctly state: "If TargetFrameworks (plural) is specified, TargetFramework (singular) is ignored."

Context

When both properties are present in a project file:

<PropertyGroup>
  <TargetFramework>net8.0</TargetFramework>
  <TargetFrameworks>net7.0;net6.0</TargetFrameworks>
</PropertyGroup>

MSBuild uses TargetFrameworks and ignores TargetFramework, regardless of declaration order.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[UUF] - TargetFramework ignored if TargetFrameworks specified</issue_title>
<issue_description>### Type of issue

Outdated article

Description

The Note for TargetFrameworks is wrong, the current behavior in Visual Studio 2022 is that when TargetFrameworks, plural, is defined, then TargetFramework (singular) is ignored.

Page URL

https://learn.microsoft.com/en-us/dotnet/core/project-sdk/msbuild-props

Content source URL

https://github.com/dotnet/docs/blob/main/docs/core/project-sdk/msbuild-props.md

Document Version Independent Id

6741b1de-38a4-fbb1-d79d-acc47d549a2d

Platform Id

eeaf76f8-da20-9011-c5e7-db6166523403

Article author

@gewarren

Metadata

• ID: cb4428fc-215c-78e1-5ff0-fe73f7a08260
• PlatformId: eeaf76f8-da20-9011-c5e7-db6166523403
• Service: dotnet-fundamentals

Related Issues</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [UUF] - TargetFramework ignored if TargetFrameworks specified #49426

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

---

Internal previews

📄 File	🔗 Preview link
docs/core/project-sdk/msbuild-props.md	docs/core/project-sdk/msbuild-props

[gewarren]

Verified the behavior.

[Copilot]

Pull Request Overview

This PR clarifies the documentation for the TargetFrameworks property by reversing the perspective of the note. Instead of stating that TargetFrameworks is ignored when TargetFramework is specified, it now explains that TargetFramework is ignored when TargetFrameworks is present, which better aligns with the property being documented.

Key Changes

• Rewording of the NOTE section to clarify the relationship between TargetFramework and TargetFrameworks properties.

[BillWagner]

This LGTM @gewarren

Let's