This works fine and dandy. But if in your form you have an async call, and other events are waiting to get fired once the response is received (as in WebBrowser control's DocumentCompleted event), then you're out of luck, because the form goes out of scope as soon as the line of code is processed (without the message box). If you leave the message box code in there, the form will run properly, but it will appear on your screen as soon as you click the mesage box. Without the message box, the form's constructor will run, but if there's code in the constructor that fires off an async call, the form will not stick around for the event to come back with the result.
Any suggestions?
Thanks!