custom error numbers

  • Thread starter Thread starter Paul Wilson
  • Start date Start date
P

Paul Wilson

I want to use Err.Raise() method to raise my own exceptions.
Is this the right way of raising my own exceptions ? (i think this is the
only way).

What is the Error number i can safely use, ensuring that it isn't used by
..NET.
Ie, can i use -100 as a error number??
Ie, -100, -101,-102... etc.
I want to konw if .NET uses negative values as error number?
(because i want a specific list of error numbers, to ensure that they are
used & ONLY raised by me in my applications).

Regards,
Paul
 
Paul,

In .NET you can create your own exception class derived from the
system.exception or system.applicationexception class and use it for your
custom error handling.

I do not think Err.Raise along with the error numbers is recommended as it
is a VB6 way where we did not have the structured exception handling.

Best Regards,
Y. Sivaram
 
Thanx Sivaram.

Y. Sivaram said:
Paul,

In .NET you can create your own exception class derived from the
system.exception or system.applicationexception class and use it for your
custom error handling.

I do not think Err.Raise along with the error numbers is recommended as it
is a VB6 way where we did not have the structured exception handling.

Best Regards,
Y. Sivaram
Click to expand...
 
* "Paul Wilson said:
I want to use Err.Raise() method to raise my own exceptions.
Is this the right way of raising my own exceptions ? (i think this is the
only way).

What is the Error number i can safely use, ensuring that it isn't used by
.NET.
Ie, can i use -100 as a error number??
Ie, -100, -101,-102... etc.
I want to konw if .NET uses negative values as error number?
(because i want a specific list of error numbers, to ensure that they are
used & ONLY raised by me in my applications).
Click to expand...

I would use 'Throw New Exception(...)' to throw simple exceptions. For
extended exceptions, you can inherit from the exception classes and
extend them. Notice that the constructor of 'System.Exception' allows
you to specify an inner exception.
 
Paul,
In addition to the others comments.

For information on using Throw to "raise errors" and Try/Catch to handle
those errors see:

http://msdn.microsoft.com/library/d...cn7/html/vaconStructuredExceptionHandling.asp


Depending on the type of application you are creating, .NET has three
different global exception handlers.

For ASP.NET look at:
System.Web.HttpApplication.Error event
Normally placed in your Global.asax file.

For console applications look at:
System.AppDomain.UnhandledException event
Use AddHandler in your Sub Main.

For Windows Forms look at:
System.Windows.Forms.Application.ThreadException event
Use AddHandler in your Sub Main.

It can be beneficial to combine the above global handlers in your app, as
well as wrap your Sub Main in a try catch itself.

There is an article in the June 2004 MSDN Magazine that shows how to
implement the global exception handling in .NET that explains why & when you
use multiple of the above handlers...

http://msdn.microsoft.com/msdnmag/issues/04/06/NET/default.aspx

For example: In my Windows Forms apps I would have a handler attached to the
Application.ThreadException event, plus a Try/Catch in my Main. The
Try/Catch in Main only catches exceptions if the constructor of the MainForm
raises an exception, the Application.ThreadException handler will catch all
uncaught exceptions from any form/control event handlers.

Hope this helps
Jay
 
Back
Top