We have been waiting to upgrade our Noesis version because we were waiting for some bugs to get fixed plus needed a spot in our schedule to do it.

I'm currently trying to update our app, which works well on 3.0.4 to the new 3.1.2 version of Noesis and I'm running into a few things I need some advice on.

1. When I load the project in Visual Studio 2019, I can't seem to attach to Unity anymore. It claims I have a ton of compile errors, many related to using namespaces. However the project runs from within the Unity editor so I don't believe i have compile issues. I'm guessing this is because Noesis is installed differently now and my project is not finding it?

2. I seem to be getting errors about UI being accessed on different threads than created it. I didn't have any issues under 3.0.4. I understand I can use Dispatcher.BeginInvoke to fix this, but I have to know where the problem is happening first, which I was trying to do with debugging. Is there any easy way to figure out where these cross-thread calls are coming from?

Thanks.

1. In 3.1 we started to deliver NoesisGUI as a package for the Package Manager (see our installation instructions), so the plugin scripts are no longer inside the Assets folder. But if you click the "Open C# project" from inside Unity it should update your Unity solution to include the code from the packages used in the project: 2. If this wasn't happening in 3.0.4 it could mean something is wrong in 3.1.2 version. If you can isolate this in a small example and report it in our bugtracker we can analyze it and fix it if there is a bug.

Ok, let me get debugging working and I'll try to isolate the issue.

I'm definitely doing UI stuff on event callback threads, which I know can cause UI-thread mismatches in WPF. However almost everything I'm doing is with binding properties, which in WPF you can update from any thread as long as it isn't a collection, so I'm assuming Noesis is the same?

I will dig into my code and see if I can figure out what is happening. We're good running with the 3.0.4 version for now but I want to get us caught up for the future.

Hi Jamieh,

In fact in Noesis we don't support notifying of property changes from different threads, so it is not the same as in WPF. I created ticket #2256 in our bugtracker to implement this because it is a very interesting feature.

What is happening then is that in previous versions we were not showing the error messages generated from other threads, and that was fixed in 3.1.1 version. So now you are seeing all those error messages of invalid thread access that were always there. Could you enqueue your PropertyChanged notifications to occur in the main thread?