Well without the flag the code doesn't compile. And VS can't attach a debugger to a project that doesn't compile. So I have to add the flag with the project hook to be able to work with Noesis at all in VS. Also what exactly does the flag do? Check for Mono? Isn't that a bit bad anyway since Unity w...

Yes I saw it and I already posted a view issues in the thread

I'm getting several errors here in Unity 5.5. After adding a XAML I get this Assertion failed on expression: '!performAutorepaint || GetApplication().MayUpdate()' UnityEditor.AssetDatabase:SaveAssets() NoesisPostprocessor:OnPostprocessAllAssets(String[], String[], String[], String[]) (at Assets/Noes...

Ok I'm having a major problem with Unity Tools for Visual Studio. Tons of types are not found like e.g. ICommand. It works in Unity but once I actually open the project in VS2015, I get all kinds of compiler errors from VS, which also doesn't allow me to work with Noesis and/or attach VS to Unity fo...

From what I know {Binding SomeProperty} is just a shortcut for Binding Path=SomeProperty, so maybe just {Binding Converter=... would work in case the Binding is necessary? I've seen this stuff before. Just a suggestion however. Instead of using a converter, can't you do a custom Markup extension for...

A quick followup qurstion to the XAML loading. If I load a XAML and get the FrameworkElement object in return. Will it be possible in the future to assign that to the NoesisGUIPanel component in Unity as a root? Right now the root can only be changed by forcing a complete reload specifying the XAML ...

I'm currently experimenting with programatically setting the root XAML of the NoesisGUIPanel by setting the xaml path and then forcing a reload with ForceLoadXaml(); Works fine but if I have the NeosisGUIPanel open in the inspector while it happens, an exception is thrown: ArgumentException: GUILayo...

Source attribute deprecated in UserControls and Code-Behind classes. Corresponding XAML must now be loaded from constructor using LoadComponent(this, uri). This matches the WPF behavior. class MyUserControl: public Noesis::UserControl { public: MyUserControl() { InitializeComponent(); } private: vo...

Well considering he pointed out that it is VERY IMPORTANT to remove the attribute, it sounded like it wouldn't even work otherwise back then. Also x:Class isn't just about code behind. As I mentioned, if I want to use a usercontrol not as the root but inside another XAML then I wouldn't know how wit...

So I found this tutorial video on your Youtube channel: https://www.youtube.com/watch?v=50aPNUYSPyA&t=608s It states that it is very important to remove the x:class attribute for a usercontrol that is used as the root element to work. Is this still the case? I'm a bit confused about this because I n...