-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 #1962
Comments
Essentials is already done for Android, but maybe not other platforms?
|
Another assembly that looks like it isn't marked for trimming is |
This behavior is not trim-compatible, since it just a random string "route name" and calls Type.GetType with it, and then Activator.CreateInstance. The trimmer might have removed the whole type, or even the constructor on the Type. This would cause a trimmed application to behave differently than an untrimmed application. I do not know of anyone who relies on this behavior, and there are no tests for it. So removing it seems like the best path forward. Contributes to dotnet#1962
This behavior is not trim-compatible, since it just a random string "route name" and calls Type.GetType with it, and then Activator.CreateInstance. The trimmer might have removed the whole type, or even the constructor on the Type. This would cause a trimmed application to behave differently than an untrimmed application. I do not know of anyone who relies on this behavior, and there are no tests for it. So removing it seems like the best path forward. Contributes to #1962
We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process. |
Closing in favor of: #18658 |
We should be able to build the library with Trimming enabled and have MAUI work in applications.
The text was updated successfully, but these errors were encountered: