-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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.
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
Make MAUI trimming safe ✂️ #355
Comments
There are a few things that will immediately help us progress here. We are moving to a more code/API based approach to registering things like handlers instead of scanning for assembly level attributes when assemblies are loaded. In areas where we still want (or need) to support these types of scenarios we can move towards using source code generators to generate the api invocations so that the linker can still be aware of usages and have them not linked out. Agree overall, being trimming safe is a priority for MAUI. |
Using source generators is certainly a step in the right direction. You can use the tooling to identify linker unsafe code today if you need to. |
Closed - tracking in #1962 |
* [Tizen] Fix BlazorWebView build error * [Tizen] Update tizen handler
* [Tizen] Fix BlazorWebView build error * [Tizen] Update tizen handler
* [Tizen] Fix BlazorWebView build error * [Tizen] Update tizen handler
* [Tizen] Fix BlazorWebView build error * [Tizen] Update tizen handler
As part of the .NET6 effort we are making the .NET Runtime trimming safe allow developers to annotate their libraries to be also trimming safe. As MAUI is one of the primary workloads which will always use linker and cares about the size it's important to resolve any linker warnings which the developers would experience when enabling linker analyzers in their apps to be able to trim their apps fully.
This will partially depend on the work done for Apple, Android and WinUI SDKs but it's not blocked by them.
The text was updated successfully, but these errors were encountered: