tags:

views:

520

answers:

1
Q: 

In vb.net, how do you force-exit an application and stifle error messages?

I want the user to simply be able to exit my application. However, for some reason, code which I have on a time delay, controlled by a stopwatch, is still trying to execute. I do not care if it tries to do so or not, but I want to stop the error and force-quit the application, terminating ALL running threads where they stand.

I am using Visual Basic Express 2008 with SP1, and I am coding in vb.net, this is a WinForm application.

I have tried simply closing the forms with Formname.Close() and I also tried Application.Exit(). I even tried an If Then statement which exited the thread which referenced my textbox, quitting it with Application.ExitThread()

I got:

ObjectDisposedException was unhandled

Cannot access a disposed object. Object name: 'TextBox'.

How can I handle this exception or simply finish exiting?

Thanks for the help!

EDIT: To clarify, I don't care how this is achieved, I just want the application to stop running, and have no errors occur.

+1  A: 

can you shut off the stopwatch before you exit?

Beth  2009-08-20 17:56:37
The stopwatch is declared from within a subroutine, it had already stopped by the time the ObjectDisposedException occurred.
Cyclone  2009-08-20 17:59:05
There may be something else going on. Try deleting your text box and/or your stopwatch and see if it exits w/o error. Try to isolate which object/condition is causing the problem.
Beth  2009-08-20 18:28:38
It is still executing the code "LoadBox.AppendText(LoadProgress.Text + Environment.NewLine)" when it has already executed. How do I stop this?
Cyclone  2009-08-20 18:44:40
Eh, I solved my problem. I simply removed the ability to quit the application at that point in time. It was a two-second process anyway, if they can't be patient for that then that stinks for them ;).
Cyclone  2009-08-20 18:56:23
glad you fixed it. sometimes the problem is simply that you're looking in the wrong place.
Beth  2009-08-20 19:17:52

related questions

What is the proper way to re-throw an exception in C#?
Is there a good way around the problems of structured exception handling (__try __except) with a multi-threaded server?
Avoid throwing a new exception
Catching exceptions as expected program execution flow control?
Exception handling using an HttpModule
Pattern for trying different methods when exception is thrown
Is there a way to determine if an exception is occurring?
Why Re-throw Exceptions?
Conditions when finally does not execute in a .net try..finally block
Use of the Exception class in c#
What are the principles guiding your exception handling policy?
Performance of try-catch in php
Exceptions: Is this a good practice?
How can I catch AWT thread exceptions in Java?
Does an application-wide exception handler make sense?
Should I catch exceptions only to log them?
How to prevent the ObjectDisposedException in C# when drawing and application exits
How to properly handle exceptions when performing file io
How to catch ALL exceptions/crashes in a .NET app
Exception handling in Delphi
Debug.Assert vs. Specific Thrown Exceptions
UnhandledException handler in a .Net Windows Service
Exception Handling in .net web apps
catching all types of exceptions in C++ in one catch block
Exceptions in Web Services