Bug: The WMC1510 warning message unexpectedly appears in the control template pulled by generic.xaml

[Gaoyifei1011]

Description

The WMC1510 warning message unexpectedly appears in the control template pulled by generic.xaml

--------------------------------------

WMC1510 警告信息意外出现在 generic.xaml 拉取的控件模板中

Steps To Reproduce

When the DefaultTeachingTipStyle (TeachingTip) control template is pulled from the generic.xaml control template, additional WMC1510 information related to AOT publishing appears when the application is compiled

--------------------------------------

从 generic.xaml 控件模板中拉取 DefaultTeachingTipStyle（TeachingTip）控件模板时，应用编译时会出现以外的 WMC1510 信息，该信息与 AOT 发布有关

Expected Behavior

The WMC1510 information should not appear in the pulled TeachingTip control template

--------------------------------------

WMC1510 信息不应该出现在拉取的 TeachingTip 控件模板中

Version Info

CsWinRT 2.2.0
Windows App SDK 1.7-preview1
Visual Studio 17.13
.net 9.0.2

Additional Context

[dongle-the-gadget]

Well it is correct here, using Binding in such a manner causes the application to fail on startup unless annotated with GeneratedBindableCustomProperty. This issue happened to the Windows Community Toolkit as well (CommunityToolkit/Windows#615).

[manodasanW]

Yes, this is a new warning we added in the xaml compiler in WinAppSDK 1.7 for Binding scenarios when publishing for AOT to ensure that any Binding use is validated to make sure it to AOT safe (either statically via X:DataType and GeneratedBindableCustomProperty or manually by the developer and suppressed as AOT safe).

[Gaoyifei1011]

Yes, this is a new warning we added in the xaml compiler in WinAppSDK 1.7 for scenarios when publishing for AOT to ensure that any use is validated to make sure it to AOT safe (either statically via and or manually by the developer and suppressed as AOT safe).Binding``Binding``X:DataType``GeneratedBindableCustomProperty

However, this control template comes from WinUI internal TeachingTip, pull the control template when the control template is only fine tuning the style of the control template, so there is no corresponding source code for the control template. I would like to ask you how I can suppress this message or modify the appearance of this warning?

[dongle-the-gadget]

NoWarn works, but it will still fail as the binding is not safe. It works for WinUI since it is C++.

[Gaoyifei1011]

NoWarn works, but it will still fail as the binding is not safe. It works for WinUI since it is C++.

Yes, this is a new warning we added in the xaml compiler in WinAppSDK 1.7 for Binding scenarios when publishing for AOT to ensure that any Binding use is validated to make sure it to AOT safe (either statically via X:DataType and GeneratedBindableCustomProperty or manually by the developer and suppressed as AOT safe).

Yes, this is a new warning we added in the xaml compiler in WinAppSDK 1.7 for Binding scenarios when publishing for AOT to ensure that any Binding use is validated to make sure it to AOT safe (either statically via X:DataType and GeneratedBindableCustomProperty or manually by the developer and suppressed as AOT safe).

Forgot to say, in the error warning prompt said can use x:SupressXamlTrimWarnings="True" to suppress warnings, but I did not find this property in XAML intelligent perception

[manodasanW]

Yes, you can use x:SupressXamlTrimWarnings="True" on the Binding and it should suppress it. Does that work? The XAML IntelliSense is not up to date on new directives that were added.

<TextBox x:Uid="TextInput1" Text="{Binding InputText, Mode=TwoWay, x:SuppressXamlTrimWarnings=True}" />

[Gaoyifei1011]

Yes, you can use x:SupressXamlTrimWarnings="True" on the Binding and it should suppress it. Does that work? The XAML IntelliSense is not up to date on new directives that were added.

<TextBox x:Uid="TextInput1" Text="{Binding InputText, Mode=TwoWay, x:SuppressXamlTrimWarnings=True}" />

I tried to add it and encountered an error during compilation

[manodasanW]

I am curious, if you look at the output window after a build rather than the error list, what is the error there?

[Gaoyifei1011]

I am curious, if you look at the output window after a build rather than the error list, what is the error there?