Hey all. I’m trying to see about handling events in a console application. I would prefer to not use silent WinForms (though I understand that that’s one way) to do it. I’ve read over a similar question and its response. See response text below (link):
The basic requirement of an STA thread is that it needs to run a message pump. In Windows Forms, you can use Application.Run. Or you could write the message pump by hand, using user32!GetMessage & DispatchMessage. But it’s probably easier to use the one in WinForms or WPF.
What the basic structure of a program that uses ‘user32 -> GetMessage’ & ‘user32 -> DispatchMessage’?
See the topic ‘Using Messages and Message Queues’ in MSDN (under Win32 and COM Development > User Interface > Windows User Experience > Windows Management > Windows User Interface > Windowing > Messages and Message Queues; you’ll probably need to take a look at the other articles and samples in the same section). Quick summary, omitting error handling and using C syntax rather than C# for reasons discussed below:
As you can see from the window setup boilerplate, this still relies on ‘silent windows,’ albeit created and message-pumped via the Win32 API rather than through WinForms. So you’re not really gaining anything by doing this way. Hence my feeling there’s not much point translating this stuff into C# — if the only solution to your problem is an invisible window, you may as well use an invisible Windows Form and all the friendly wrappers that come with that platform.
However, if you’re not actually using a Windows Forms control like the poster of the linked question, then you can quite happily use .NET events in a console application. The restriction to STA and the need for a message pump is specific to receiving events from WinForms and ActiveX controls like the WebBrowser (or messages from Win32 HWNDs, though that doesn’t necessarily require STA).