Not an issue, but a shot in the dark.

[Noemata]

I was wondering if you could share some of the bits from your XAML Studio project. I'm curious about how you resolve namespaces from the loose XAML you load and whether it might be possible to load DLL's dynamically to add to the namespaces that could be resolved?

A simple example would be very helpful.

If you'd like to continue this conversation privately, I'm open to sorting out an exchange of emails through linkedin or other less open area.

[michael-hawker]

Hey @Noemata, I'm hoping I can eventually open source XAML Studio, but I don't have a timeline for that at the moment. Resolving namespaces was just done using some reflection based on the loaded assemblies, similar to what we do in the toolkit sample app here, and the manual list of namespace helpers provided in the settings panel, nothing too magical. I just looked for the items in order to add them into the XML before I passed it to XamlReader.

Unfortunately with UWP, all the assemblies have to be baked into the package as extensions don't work the same way. Maybe with WinUI3 and the desktop app model, this could be improved in the future?

Hope that helps for now?