Rider has fantastic integration with Unity so I'd expect that a lot of people are using it. Considering that Rider also has a XAML Designer, it'd be the ideal IDE to work with Noesis in Unity.

Well.. editing those strings is a bit of a pain so I'll probably just wait for the release. Aside from that error log everything actually works. So the template gets parsed fine and also runs. it just reports that error. I can live with that for the time being.

Ah gotcha. I can do that. I should be able to put them into my bootstrapper component. As for XamlReader taking a string, please keep that. I'm using that to generate placeholder datatemplates like Caliburn. So if a view isn't found, I'm generating a DataTemplate with a magenta background and atextb...

No it's not the UserControl. The first time it happened the named element was a DockPanel. Right now it's a TreeView in a File Dialog I made. I need to name that since I want to attach an event hander in code behind.

Is it maybe because right now I'm putting the datatemplates into the Resources of root control instead of the Application resources (which I only will be able to access in the next version)? Is that causing this issue?

I'm putting them into NoesisView.Content.Resources now. Is that an issue?

Hot reloading does not seem to be the issue no. I just upgraded to Unity 2020.3.6f1 and this still happens. So I don't think Unity is to blame. And yes everytime I open the Editor now and then try to play my scene, I get the error and need to manually reimport my XAML views. I even deleted my entire...

I keep having this problem unfortunately. Everytime I give something a name, NOESIS keeps reporting it as duplicated. Also for a while now, every time I open Unity, my project complains about XAMLs being missing, until I manually reimport them. Something is going on here. I'd appreciate some help fi...

I recently ran across this article again https://www.codeproject.com/Articles/38507/Using-the-WPF-FocusScope I know this FocusScope issue has been around since forever. People would like to use it, then get surprised by what it actually does and by what WPF internally uses it for. I always thought t...

Absolutely. In fact that's usually how you do nesting of controls and navigation in WPF applications. Usually you do some databinding and work with viewmodels however. In fact I'm currently working on a framework for that. But the idea is basically you have a viewmodel, which has a property of child...