Add breaking change documentation for DynamicallyAccessedMembers annotation removal in .NET 10 #47525
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.
This PR adds comprehensive breaking change documentation for the removal of
DynamicallyAccessedMembers
annotations from trim-unsafe Microsoft.Extensions.Configuration APIs in .NET 10 Preview 6.Changes Made
New Documentation
docs/core/compatibility/extensions/10.0/dynamically-accessed-members-configuration.md
.github/prompts/breaking-change.md
Updated Navigation
docs/core/compatibility/toc.yml
docs/core/compatibility/10.0.md
Breaking Change Summary
The change removes
DynamicallyAccessedMembers
annotations from Microsoft.Extensions.Configuration APIs that were already marked asRequiresUnreferencedCode
. This affects trimming behavior by reducing the amount of code preserved during trimming, making these APIs work with even more limited use cases while still generating trimming warnings.Impact: Binary incompatible
Recommended Action: Migrate to the binding configuration source generator
Affected: APIs that generate trimming warnings in Microsoft.Extensions.Configuration
The documentation provides clear guidance for developers on understanding the impact and migration path to trim-safe alternatives.
Fixes #47433.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.
Internal previews