App works in VS's Debug mode, but does't work in run mode!

[blackjack2150]

Hi.
This one is really strange and annoying.
The main method of a Windows Application:

static void Main(string[] args)
{
Application.EnableVisualStyles();
Application.SetCompatibleTextRenderingDefault(fals e);

try
{
Application.Run(new MainForm());
}
catch (Exception ex)
{
MessageBox.Show("Caught exception in Main method.")
}
}

I've put the Run method inside a try-catch block.

When an exception is caught inside a method that belongs to the MainForm class, I throw that exception, expecting to see the MessageBox called from the Main method.

Things happen as expected when I run the program in debug mode form VS.

However, if I run the exe file directly from the Debug folder of my project, the program behaves differently, in the sense that the message box does not pop up anymore, and instead the much-hated "Unhandled exception has occured in your application." window shows.

The same happens if I generate a beep on the PC speaker(System.Console.Beep()) instead of showing the message box.

I really don't understand. Why is the exception caught only in Debug mode??

Thanks.

[kenobewan]

Its happened because your code did not get a chance to run before an error occurred. Unfortunately, you stuck with old fashioned debugging parsing the code until it works and then building it back up again. BTW - I believe that the VS debugger is better at vb.net rather than C#.

[Plater]

Are you purposely triggering an exception to test out the try catch block?
Because if not, one solution would be to just FIX the error so it doesn't happen.

Also that's not a place that's garunteed to catch every exception. Threads are invoked internally for window creation and if an exception happens on another thread, it doesn't always make it's way back to the calling thread. Leaving the exception uncaught

[blackjack2150]

Thank you. Someone suggested a shady workaround, but it seems to do the trick. Here it it:

Add

Application.ThreadException += new System.Threading.ThreadExceptionEventHandler(Appli cation_ThreadException);

before calling Application.Run(... and the corresponding event handler like this:

static void Application_ThreadException(object sender, System.Threading.ThreadExceptionEventArgs e)
{
throw e.Exception;
}


Now every exception will be caught by your "top level" try/catch.

[blackjack2150]

Are you purposely triggering an exception to test out the try catch block?
Because if not, one solution would be to just FIX the error so it doesn't happen.

I can't be certain that no error will occurs. The application connects to a database and a exception could occur if the user misspells his username at login.

Damn, I hate to see things behaving differently than what logic and common sense tells they should behave.

[Plater]

You should have smaller try/catch blocks surrounding those kinds of things