Any comments on the API stuff from the devs?

Considering there are a lot of breaking changes, like the noesisGUIPanel being a NoesisView now and the way code behind is added and how XAMLs are assets now I'd really suggest you go for 2.0. 1.3 suggests only updates and feature additions. 2.0 signals more that this includes major API and workflow...

Further API differences I ran into: Caliburn is trying to hook into the FrameworkElement.Loaded and FrameworkElement.Unloaded events. In WPF both are events based on a RoutedEventHandler . Noesis used their own event handlers called FrameworkElement.LoadedHandler and FrameworkElement.UnloadedHandler...

That might help. I'll have to look into it. But there are still some API differences, collections that dont implement IEnumerable etc that need adjusting. I'll summarize the changes I had to make or problems I'll ran into sometime this weekend. Would anybody be interested in collaborating on this? I...

Please create a ticket in our bugtracker asking for the EventTrigger.EventName property, and another one for the XamlReader.Parse(string xaml). 1025 I'll check tomorrow if there was some other stuff needed for RoutedEvents. I found some event handlers that don't match the WPF version too. I'll dig ...

From what I know that doesn't work for DataTemplates sicne they're not visual elements but templates for elements. There used to be a WPF API with a class called FrameworkElementFactory or something like that. Instead of the elements themselves you needed to create factories for them so once the dat...

Caliburn supports two kinds of conventions for binding. Property conventions and Action conventions. they're based on the x:Name of the control. The property convention works like this: <TextBox x:Name="FirstName" /> will get it's Text property automatically bound to a FirstName string property on t...

Pretty much everything works in terms of API except where the message conventions are concerned. There I'm running into a lot of missing API. First of all XamlReader is missing, which is used in Caliburn to create some basic DataTemplates on the fly. Then a lot of stuff regarding AttachedProperties ...

I'm currently trying to port Caliburn.Micro to Noesis. It's going fine for the most part actually. (The property binding conventions seems to work perfectly fine) The biggest issue are it's automatic Message Binding conventions. I'm running into missing APIs left and right. Would it be ok if I post ...

Is there any way to create a DataTemplate in code? The usually recommended way in WPF is using XamlReader.Parse() which is not available in NOESIS. Any alternatives?