Thanks for the time.
Having a Delphi backgound I am used to raising exceptions for almost anything that could go wrong. I'd catch the exception, add a user friendly message and raise another exception. This is more a VS Editor related question than exception handling itself.
The thing is whenever I throw a new exception outside of a try...catch block a "Exception was unhandled" dialog box appears and the editor will not continue execution. When running the EXE this functionality work as I require it to, but while debugging I would like to continue and the exception should be displayed on sceen. I'm sure this is a new addition to the Express edition.
Throwing new exceptions is a nice way for me of knowing that all processing for the current business process is stopped because something went wrong, and that a message would be displayed to the user indication what went wrong. If there is no way around this I would have to return boolean values for alot of my function indicating if something went wrong. For debugging puroses at least so that I can continue execution.
I've tried disabling some options in Tools->Options->Debugging.
In the help file under "Continue Execution After an Exception" they say that one can continue execution in the same thread after an unhandled exception. In native C/C++ the Exception dialog box reappears if you have not fixed the problem. The debugger keeps getting stuck where I've thrown my last exception.
I guess I'll have to adapt my programming style if I don't find a way around this.
Something that may help is throwing a "silent exception", similar to the abort command in Delphi.
What to do Can anybody help me please!
Thanks.
Visual Studio 2005 Express Edition: Continue execution after unhandled exception
Hot Topic
- C# - Namespaces - accessing of sub-namespaces
- functions
- Can C# do this??
- Threading in C#
- Forcing VS2K5 not to use partial classes (reverting to 2K3 behavior)
- Text Highlighting
- ScrollBars on MDI Application
- Is it possible to serialize to XML with comments?
- Restarting an App programmatically using C#
- Transferring data from one form to another, is it possible?
Visual C#
- Increase Memory Pressure for Garbage Collection
- Application settings.
- Word object and its Enumerations
- what am i missing
- Configuration Application Block
- Dvd LG 4167B problem
- Serilization of a generic List of a custom type, how?
- Iterating over an enum
- Passing Values
- Singleton pattern WITH command-line passing?
Visual Studio 2005 Express Edition: Continue execution after unhandled exception
Lori D. Pearce
Exceptions are expensive and slow. If you throw and do not catch, it bubbles to the top of your app, and no resume is possible at that point. You need to catch your own exceptions, and use them only where you can afford to lose a few second execution time.