Skip to content

Add trim incompatibility to TOC #26717

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 28, 2021
Merged

Add trim incompatibility to TOC #26717

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/core/deploying/trimming/trim-self-contained.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ However, there is a risk that the build time analysis of the application can cau
## Components that cause trimming problems

Any code that causes build time analysis challenges, isn't suitable for trimming. Some common coding patterns that are problematic when used by an application originate from unbounded reflection usage and external dependencies that aren't visible at build time. An example of unbounded reflection is a legacy serializer, such as [XML serialization](../../../standard/serialization/introducing-xml-serialization.md) and an example of invisible external dependencies is [built-in COM](../../../standard/native-interop/cominterop.md). For known incompatibilities, see [Known trimming incompatibilies](incompatibilities.md). To address trim warnings in your application, see [Introduction to trim warnings](fixing-warnings.md), and to make your library compatible with trimming, see[Prepare .NET libraries for trimming](prepare-libraries-for-trimming.md).
Any code that causes build time analysis challenges, isn't suitable for trimming. Some common coding patterns that are problematic when used by an application originate from unbounded reflection usage and external dependencies that aren't visible at build time. An example of unbounded reflection is a legacy serializer, such as [XML serialization](../../../standard/serialization/introducing-xml-serialization.md) and an example of invisible external dependencies is [built-in COM](../../../standard/native-interop/cominterop.md). For known incompatibilities, see [Known trimming incompatibilies](incompatibilities.md). To address trim warnings in your application, see [Introduction to trim warnings](fixing-warnings.md), and to make your library compatible with trimming, see [Prepare .NET libraries for trimming](prepare-libraries-for-trimming.md).

## Enabling trimming

Expand Down
4 changes: 3 additions & 1 deletion docs/fundamentals/toc.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1521,7 +1521,7 @@ items:
- name: Suppress compatibility errors
href: ../compatibility/compatibility-suppressions.md
- name: Package validation diagnostic IDs
href: ../compatibility/diagnostic-ids.md
href: ../compatibility/diagnostic-ids.md
- name: Execution model
items:
- name: Common Language Runtime (CLR)
Expand Down Expand Up @@ -1601,6 +1601,8 @@ items:
href: ../core/deploying/trimming/trim-self-contained.md
- name: Intro to trim warnings
href: ../core/deploying/trimming/fixing-warnings.md
- name: Trim incompatibilities
href: ../core/deploying/trimming/incompatibilities.md
- name: Options
href: ../core/deploying/trimming/trimming-options.md
- name: Trimming libraries
Expand Down