Going into summer break with this project :) Hoping for the additional API to get this where it needs to be at the end up summer :)
I might reduce the scope slightly from a few ideas I had initally but I'd like to at least get the windowing and dialog system in there :)
And maybe the transitions.

Is your application exclusively Noesis UI or is there more to capture? If you just need to capture what Noesis does, then you could use these approaches
provided Noesis provides all the necessary API equivalents

https://stackoverflow.com/questions/512 ... wpf-window

Hmm. Not sure if that's a great idea with the folders. That would force a folder structure. Here's a suggestion though. What about an extension in XAML so we can provide a resource dictionary dependency in XAML. WPF would ignore it while you can parse it for both the preview and the correctness chec...

These things exist for serializer libraries already. But those all have dependencies on that specific serializer since they also add formatters. For Noesis, especially for the Blend project outside Unity, it would be very helpful to have a nuGet Package with shims for the Unity standard structs: (Ve...

Couldn't we add something to the settings somehow to indicate which Xamls depend on such a dictionary or something? I mean right now the global applicationdictionary XAML from the settings is obviously used to verify the XAML staticresources. Couldn't I we specify the other scene dictionaries there ...

Actually, come to think of it.... couldn't I make a serialized field on my bootstrapper monobehavior that hold a NoesisXAML ResourceDictionary (like your settings asset for the application resources), then, when the boostrapper starts up, add that dictionary to the applicationresources.mergeddiction...

Yes. I also added something in case the view is used in multiple places against the same viewmodel. The framework now automatically adds an attached property containing a location ID to the parent Visual so the framework caches them in the viewmodel by location. but yes the UserControl always gets i...

Yeah.. the problem with that is that it needs to work like in WPF, putting those .cs files in a folder where Unity finds them, where IDE's understand them, but where they don't clutter the project...

What about a property on the Noesis view where I can attach a ResourceDictionary.xaml, and those resources will be merged into the application resources on scene load, but also removed from it again on scene unload? Would that work? In a final application I think I could live with just one, although...

In WPF whenever a static resource is used, the process is like this: The lookup process checks for the requested key within the resource dictionary defined by the element that sets the property. The lookup process then traverses the logical tree upward, to the parent element and its resource diction...