EventTriggerBehavior AOT Warning

[ghost1372]

double click on error navigated to this:

[devsko]

I have absolutely no idea, if that is the best way to get it working but it works for me

1. Ensure the referenced event is rooted. In my app i added [DynamicDependency(nameof(ButtonBase.Click), typeof(ButtonBase))] to the ctor of the control that uses the behavior.
2. Add UnconditionalSuppressMessage for the method that you are navigated to by the warning. Because it is generated code, you have to add it with Scope/Target. Something like this:

 `[assembly: UnconditionalSuppressMessage("Trimming", "IL2026", Scope = "member", Target = "~M:App1.App1_XamlTypeInfo.XamlTypeInfoProvider.Activate_93_EventTriggerBehavior~System.Object", Justification = "DynamicDependency added")]

3. Every time you change the structure of your XAML, the id (93) changes and you have to adapt the suppression
4. For whatever reason the IL compiler does not recognize these Scope/Target attributes. That's why i added the following to suppress all trim warnings (with conditional compilation in case of creating the package)

namespace App1.App1_XamlTypeInfo
{
    [UnconditionalSuppressMessage("Trimming", "IL2026", Justification = "DynamicDependency added")]
    partial class XamlTypeInfoProvider
    { }
}

/cc @Sergio0694 It would be very nice to get any "official" advice how to deal with trim warnings from XAML generated code

[Sergio0694]

This is by design, and that behavior is fundamentally not trim-safe. The official advice is: don't use that behavior 🙂

[sylveon]

See #309