l>>
Cc: "mono-list@lists.ximian.com<mailto:mono-list@lists.ximian.com>"
<mono-list@lists.ximian.com<mailto:mono-list@lists.ximian.com>>
Subject: Re: [Mono-list] Mono, Windows Forms, and Headless operation
Hello,
ThreadPools are available on .NET 2.0, just not the
m>"
<mono-list@lists.ximian.com<mailto:mono-list@lists.ximian.com>>
Subject: Re: [Mono-list] Mono, Windows Forms, and Headless operation
Hi Miguel,
Thanks for the response. After digging into the mono source a bit, as well as
writing a few test programs, I’ve discovered a bit more.
Hello,
ThreadPools are available on .NET 2.0, just not the fancier TPL-based ones.
Perhaps you could consider replacing that bit of code with using the
ThreadPool?
Miguel
On Thu, Jan 7, 2016 at 4:24 PM, George, Glover E ERDC-RDE-ITL-MS <
glover.e.geo...@erdc.dren.mil> wrote:
> Hi all,
>
>
Hey George
In a couple of places you mention you don't want to see the GUI and only
needed background workers? u think using normal threads will do the trick.
You can do everything and more that the background wonder does. Check
http://www.albahari.com/threading/ for more help.
Cheers
Mladen
On
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
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
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
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
I have been trying to port my windows winforms app to Mac.I have managed to
port it successfully by replacing winforms with gtk#.Background worker has
some issues when there was concurrent execution,i switched to threads
,threads gave some other issues so i switched back to background worker and
Hello George,
> Question First:
> The main question I had for the Mono list is this. Is it possible to have
> mono run Windows Forms code without trying to open X11 (I.e. headless mode)?
> What triggers mono to request an X11 display? Is it the project type? Is it
> the call to an object that
Hello Netgear,
> -Mono(Mono.Mac not Xamarin.Mac) support is non existent.You can see this
> forum is full of spam and rarely someone replies.
I don't think the original poster is refering to Mono.Mac? X11 is not OSX ;)
And the mono list itself is quite clean from spam. You are using the
nabble
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 have
X11, mono fails to run Windows Forms code with the
13 matches
Mail list logo
