Thanks Jordan.
It turns out, I may have been conflating two problems into one. The fact
that I needed to show the windows form was because I needed a message loop
to process the BackgroundWorker¹s events. Turns out I can just call
Application.Run() with no parameter, and it will cause the UI thr
I think the advice would generally be:
1. Yes you can absolutely write a Console Application, which works perfectly
cross-platform, and does not need any WinForms or X11. (Right click your
solution, new project, Console Application). It's better to create a new
project than to convert an existi
On 07.01.2016 22:24, George, Glover E ERDC-RDE-ITL-MS wrote:
Hi all,
We’re currently porting a Windows Forms Application to Mono, and have
generally had great success. However, we have now hit a critical
decision point, and were hoping for some guidance on the best route
forward. If we don’t
Again, I agree with the separation of business logic from the GUI. In
fact, on mono, I never want to see the GUI. It¹s due to the fact that my
parallelism relies on multiple concurrent BackgroundWorkers. I¹m
restricted to .net 2.0 , nothing later. So I don¹t have the TPL
available. I have Back
Hi Timotheus,
Thanks for your reply. Unfortunately, changing from WinExe to Exe doesn¹t
help as it still wants an X Display. Also, most of the business logic is
separate from the gui . However, the multithreading uses Background
Workers, which to my knowledge, requires an event loop to handle t
