how can we trim dll unused?

[srxqds]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I have found some dll like diagnostic should not used in product release:

Expected Behavior

no loading these assembly, or can config some assembly not loading

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

6.0 blazor webasembly

Anything else?

No response

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[ghost]

Tagging subscribers to this area: @agocke, @sbomer, @vitek-karas
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I have found some dll like diagnostic should not used in product release:

Expected Behavior

no loading these assembly, or can config some assembly not loading

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

6.0 blazor webasembly

Anything else?

No response

Author:	srxqds
Assignees:	-
Labels:	untriaged, area-Tools-ILLink
Milestone:	-

[vitek-karas]

These dlls contains functionality like ability to print out stack trace (used when you call Exception.ToString), tracing support (ability to collect things like counters and so on), and support for some debugging functionality.

For the most part developers want these features even in their published applications so that it's easier to diagnose issues which happen in production.

Some of these can be disabled via properties:
https://learn.microsoft.com/en-us/dotnet/core/deploying/trimming/trimming-options?pivots=dotnet-7-0#trimming-framework-library-features

If you just change the property values the functionality will be disabled, but the code will still be there (along with the above dlls). To remove most of the associated code you would also need to trim the application: https://learn.microsoft.com/en-us/dotnet/core/deploying/trimming/trim-self-contained

Note that even in trimmed application it may be that some of these dlls will still be there (although probably smaller), it depends which APIs the application uses and how.

[agocke]

Closing as question seems answered.

@srxqds mentions that they're using Blazor, so they're probably already trimming. If the question is about figuring out what is being rooted in these types and why, I think that's a duplicate of #78671