Hello,

In Unity App.xaml is not available so we offer in Noesis Settings an 'Application Resources' where you can set a dictionary with the resources of the application.
You can create a Resources.xaml like this:

<ResourceDictionary xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"

xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"

xmlns:local="clr-namespace:MapMakerUI.Assets.UI">

<ResourceDictionary.MergedDictionaries>

<ResourceDictionary Source="Images_UI.xaml"/>

<ResourceDictionary Source="ControlStyles.xaml"/>

<ResourceDictionary Source="Templates.xaml"/>

</ResourceDictionary.MergedDictionaries>

</ResourceDictionary>

Let me know if you need more help with this.

Yes that got my custom controls working. Thanks. I figured it was something trivial.

However, for clarity, shouldn't it be possible to make Noesis debug log the fact that it is coming across references to resources that it doesn't know how to resolve? Loading the root page is loading items that reference a template that it doesn't know exists, so I would think that would be a nice time to print a warning about being unable to resolve template x or whatever. Blend is very nicely verbose with its debug output printing. I tried running it in the broken state on all the Noesis log levels to see if I could get any hints and got nothing.

I just confirmed that WPF doesn't raise any errors or warning messages when using DynamicResouces that cannot be resolved. It is Blend the only one that gives you some warning hint (blue underline) when it thinks a DynamicResource wouldn't resolve, although it could be wrong as the resource can be added later in code.

In Noesis we don't log any warning neither, because when a DynamicResource cannot be resolved the property should fallback to the default value.

Using StaticResources otherwise will give you a clear error message when the resource is not found.