Could you please report this crash and attach the crash dump that Unity generates? We shouldn't crash Unity editor.
Crash report:
https://www.noesisengine.com/bugs/view.php?id=1964
Do you have any suggestion on how we can improve that workflow? We will be glad to hear it.
I cannot recommend anything beyond getting as close to the WPF API as possible. Any changes that are necessary are an additional obstacle and it is really
hard to find any documentation on your page that describes the differences. So usually when you run into a problem you're just on your own to figure out how your version of the API
is intended to be used.
So my recommendations: Massive effort to keep every bit of API identical to WPF and where that isn't possible or changed for a reason add easy to find and easy to understand documentation explaining the difference and how to use it, how to work around the difference to achieve the same result. And that documentation needs to be both online AND in the code itself so people find it with intellisense.
When I use one of your APIs and a parameter is missing compared to WPF then I have no idea why or how I'm supposed to adjust for that. That's usually the main issues I run into.
It's not that Noesis doesn't work, it's that I keep running into API differences that I don't have any information on, so every single one of them blocks me in my work as I have no information on how to proceed.
And coming to the forums and wait a couple hours for someone to explain it is not a sustainable workflow. That needs to be easier. I understand API changes are sometimes appropriate or necessary, but that needs to be explained.
Unlike a completely new API, this is an API that is based on an incredibly well established one. One I for example use every day of the week. When something doesn't work as I am used to, I get stuck. I rely on WPF's documentation on how to solve problems. When Noesis does it differently there's basically no documentation at all on the why or how.