Very interesting, thanks for the detailed info! So my mental model of how Noesis works was wrong, I believed Noesis was like WPF, always sending messages to a DUCE thread that performs the native rendering. I looked at my code and indeed, I first call m_NoesisWrapper.Update(gameTime); , and then I u...

Instead of Robocopy, I just have a separate WPF project and use file links the Noesis XAML files, so copying is not needed. That being said, my demo project only has two XAML files, so I'm not sure how robust it is.

https://msdn.microsoft.com/en-us/librar ... .105).aspx

Nevermind, I think I solved the problem.

I'm I correct to assume that Noesis does not have a separate render thread? It has an extra thread for performing tessellation and triangulation, but the rendering itself is done on the main thread, using the Direct3D immediate device context?

Very wise words. HTML5 works really well if you just use the features that a typical web page uses. Otherwise you're on thin ice, although maybe these days stuff is more stable (two years ago I remember going through Blink source after null ref exceptions, and read stuff like 'todo: handle device lo...

But obviously no Resharper support ;-) But a great initiative! XAML is indeed rather bulky. Now in a really good designed language like Haskell, one never needs to invent another language, one just uses the main language to define DSLs. Mmm, Haskell bindings to NoesisGUI, that would be interesting ;...

I am using an image brush to render parts of a large monogame render target This works fine when the render target and brush view box coordinates are not changing, but as soons as the render target or the view box coordinates are updated, Noesis seems to pick the wrong parts of the monogame texture,...

Thanks a lot for all these points! I have to justify to the investors why I picked Monogame and Noesis, and this really helps. I just followed my gut feeling. And although I worked 25 years in the game and graphics field, people prefer to read hard facts ;-) I already dropped HTML5 as a platform, af...

Nice! Off topic, but may I ask you why you are using Monogame instead of Unity for your project? In my case it's because (1) Monogame is open source and I'm a control freak ;-) (2) My app is mostly about generating 2D content and doing realtime CSG, and Unity doesn't really provide any benefits here...

Yes I reverted my code to do the same as yours again, now it works, I pushed it. I still have troubles getting all text input working correctly. I had to do a lot of hacks. For example, when pressing ENTER the first time, Noesis does not seem to perform a linefeed in its textbox, only a CR. Looking ...

Ah, I recall that I simplified the PreRender and PostRender steps into a single render call. But indeed that must have broken something. I'll revise. Thanks!