Microsoft.Toolkit.Uwp.UI.Controls.Core/Resources ResourceMap Not Found

[Manohar-Gunturu]

Line throwing the error 'ResourceMap Not Found':

WindowsCommunityToolkit/Microsoft.Toolkit.Uwp.UI.Controls.Core/InAppNotification/InAppNotification.cs

Line 70 in 2d608fd

AutomationProperties.SetName(_dismissButton, "WCT_InAppNotification_DismissButton_AutomationName".GetLocalized("Microsoft.Toolkit.Uwp.UI.Controls.Core/Resources"));

We have defined our own InAppNotificationAlias.Template and this line has been crashing the app on Win10. Is our app supposed to access Microsoft.Toolkit.Uwp.UI.Controls.Core/Resources, or do we need to define the WCT_InAppNotification_DismissButton_AutomationName string in the app's resource file?

[ghost]

Hello Manohar-Gunturu, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

[michael-hawker]

This is defined by the Core package itself here:

WindowsCommunityToolkit/Microsoft.Toolkit.Uwp.UI.Controls.Core/Strings/en-US/Resources.resw

Lines 136 to 139 in 2d608fd

	<data name="WCT_InAppNotification_DismissButton_AutomationName" xml:space="preserve">
	<value>Dismiss</value>
	<comment>The automation name for the dismiss button of the InAppNotification control.</comment>
	</data>

There shouldn't be a reason for it not to be found. Unless if you custom template doesn't have a dismiss button maybe? Otherwise, you should be able to define the full resource string in your app.

In either case, InAppNotification won't ship in the upcoming 8.0 release. It's been replaced with the StackedNotificationsBehavior on top of WinUI's InfoBar control. So, I'd recommend that approach moving forward with the incoming 8.0 release.