Add multi-targeting sections to trimming and AOT documentation

[Copilot]

Adding multi-targeting sections to trimming and AOT documentation

• Explore repository structure and understand the issue
• Review current documentation in prepare-libraries-for-trimming.md
• Review related breaking change document
• Add new H2 section "Multi-targeting for trimming" after "Enable library trim warnings"
• Include recommendations for multi-targeting scenarios
• Add example showing conditional IsTrimmable usage
• Explain common multi-targeting scenarios (netstandard2.0, net472, net6.0+)
• Link to breaking change document
• Verify markdown linting passes
• Update document metadata date
• Address review feedback - simplify section to brief statement + example
• Clarify multi-targeting recommendation to avoid TFM gaps
• Move IsAotCompatible multi-targeting guidance to AOT docs
• Update AOT docs to use net8.0 (earliest version with AOT compat analysis)
• Update SDK error messages to specify net6.0 for trimming, net8.0 for AOT
• Add recommendation to include latest .NET version for latest analyzer
• Update examples to use net10.0 as latest version
• Add Oxford commas to framework lists per writing style guidelines
• Break up long sentences for better readability (initial)
• Merge conflicts resolved with main branch
• Clarify multi-targeting benefits for analyzer support
• Section rewritten by @sbomer for clarity
• Add Oxford commas and fix grammar per Copilot reviewer feedback
• Break up long sentences per @sbomer's request
• Final review and validation

Summary

Per @sbomer's request based on Copilot reviewer feedback:

• Broke up long sentences in both trimming and AOT sections
• Changed "target the latest supported TFM to benefit from the latest analyzer improvements" into separate sentences: "target the latest supported TFM. This helps you benefit from the latest analyzer improvements."
• Changed "At a minimum, target net6.0/net8.0 or later, which is required for trim/AOT analysis warnings" into separate sentences: "At a minimum, target net6.0/net8.0 or later. This version is required for trim/AOT analysis warnings."
• Applied changes to both trimming and AOT documentation sections
• All files pass markdown linting

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Prepare .NET libraries for trimming: Add multi-targeting H2 with our recommendations</issue_title>
<issue_description>
See this comment copied below

Finally, recently we've learned that multi-targeting is not only very common, but basically a must have when enabling trimming. (This is based on experience trying to make some NuGets trim compatible). I think the document should have a section about the multi-targeting and our recommendations around it. But the core point is that very few libraries will only target latest TFM. By far the most common case is either library targets netstandard2.0 or it multi-targets net472, netstandard2.0 and net6.0 (or some combination of these).

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: f3d1f980-933d-a2a8-1645-098c2a4bc2a2
• Version Independent ID: 80dc5a35-aee1-fa68-5a21-78c628e9ff41
• Content: Prepare .NET libraries for trimming - .NET
• Content Source: docs/core/deploying/trimming/prepare-libraries-for-trimming.md
• Product: dotnet-fundamentals
• GitHub Login: @sbomer
• Microsoft Alias: svbomer</issue_description>

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

@sbomer Leaving a note here to mention the new behavior in the `true` part of https://learn.microsoft.com/dotnet/core/deploying/trimming/prepare-libraries-for-trimming. @sbomer I'm adding a breaking change notice that mentions multi-targeting: https://github.com//pull/36775. We still need a dedicated section in the general trimming docs though. When that's added, we should also link to it from the breaking change notice.

• Fixes Prepare .NET libraries for trimming: Add multi-targeting H2 with our recommendations #36730

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

---

Internal previews

📄 File	🔗 Preview link
docs/core/deploying/native-aot/index.md	docs/core/deploying/native-aot/index
docs/core/deploying/trimming/prepare-libraries-for-trimming.md	docs/core/deploying/trimming/prepare-libraries-for-trimming
docs/core/tools/sdk-errors/index.md	docs/core/tools/sdk-errors/index

[sbomer]

@copilot Add a similar note for IsAotCompatible (alongside the existing docs for that option).

[Copilot]

@copilot Add a similar note for IsAotCompatible (alongside the existing docs for that option).

Added in 78f6612. The note directs users to apply the same multi-targeting guidance when using IsAotCompatible in multi-targeted projects, with a link to the "Multi-targeting for trimming" section.

[sbomer]

@copilot fix merge conflicts

[Copilot]

@copilot fix merge conflicts

Resolved in d2e8293. Merged main branch and kept both the "Multi-targeting for AOT compatibility" section (from this PR) and the new "Verify referenced assemblies are AOT-compatible" section (from main). Both sections now appear in the correct order.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 8 comments.