Get Error Number

[RP]

If an exception occurs, how to get the error number. I mean, is there
anything like ex.number?

[John Duval]

On Oct 10, 2:04 pm, RP <rpk.gene...@gm ail.comwrote:

If an exception occurs, how to get the error number. I mean, is there
anything like ex.number?

Hi RP,
There really isn't anything equivalent to an error number in .NET --
typically the type of the exception object thrown is what is used to
do runtime error handling. And the message in the exception is
typically what is shown to the user, not a number. There are some
types of exceptions that have error numbers (see
COMException.Er rorCode) but I think in the new .NET world, the error
number has gone by the wayside.

Is there a particular case where you need to get at the error number
(a la GetLastError from the Win32 days)?

John

[Jon Skeet [C# MVP]]

RP <rp*********@gm ail.comwrote:

If an exception occurs, how to get the error number. I mean, is there
anything like ex.number?

For many exceptions there *isn't* an error number - after all, you can
create whatever exception you want and throw it.

You can use Exception.HResu lt in some cases, but don't rely on it
always being present.

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

"RP" <rp*********@gm ail.comwrote in message
news:11******** **************@ 19g2000hsx.goog legroups.com...

If an exception occurs, how to get the error number. I mean, is there
anything like ex.number?

Not really, you can get the message of the exception and even the stacktrace
that indicate in which method the exception was thrown.

[Chris Mullins [MVP - C#]]

"Jon Skeet [C# MVP]" <sk***@pobox.co mwrote in message
news:MP******** *************@m snews.microsoft .com...

RP <rp*********@gm ail.comwrote:

>If an exception occurs, how to get the error number. I mean, is there
anything like ex.number?

For many exceptions there *isn't* an error number - after all, you can
create whatever exception you want and throw it.

heh. Perfectly valid, if not quite correct, code...

Object errorNumber = (object) 101;
throw errorNumber;

One day I'm going to figure out why any arbitrary thing can be thrown,
rather than constraining it to only Exceptions...

--
Chris Mullins

[Nicholas Paldino [.NET/C# MVP]]

Actually, it's not valid C# code. While the CLR does allow for objects
to be thrown, in C#, the compiler requires that the target of the throw
statement derive from System.Exceptio n.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m
"Chris Mullins [MVP - C#]" <cm******@yahoo .comwrote in message
news:%2******** ********@TK2MSF TNGP02.phx.gbl. ..

"Jon Skeet [C# MVP]" <sk***@pobox.co mwrote in message
news:MP******** *************@m snews.microsoft .com...

>RP <rp*********@gm ail.comwrote:

>>If an exception occurs, how to get the error number. I mean, is there
anything like ex.number?

For many exceptions there *isn't* an error number - after all, you can
create whatever exception you want and throw it.

heh. Perfectly valid, if not quite correct, code...

Object errorNumber = (object) 101;
throw errorNumber;

One day I'm going to figure out why any arbitrary thing can be thrown,
rather than constraining it to only Exceptions...

--
Chris Mullins

[RP]

In VB.NET we have err.Number.

[=?Utf-8?B?UGV0ZXIgQnJvbWJlcmcgW0MjIE1WUF0=?=]

According to Michaelis, "In C# 2.0, all exceptions, whether deriving from
System.Exceptio n or not, will propagate into C# assemblies as derived from
System.Exceptio n. .... the CIL code corresponding to an empty catch block is,
in fact, a catch(object) block..."
-- Peter
Recursion: see Recursion
site: http://www.eggheadcafe.com
unBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder: http://www.blogmetafinder.com

"Nicholas Paldino [.NET/C# MVP]" wrote:

Actually, it's not valid C# code. While the CLR does allow for objects
to be thrown, in C#, the compiler requires that the target of the throw
statement derive from System.Exceptio n.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m
"Chris Mullins [MVP - C#]" <cm******@yahoo .comwrote in message
news:%2******** ********@TK2MSF TNGP02.phx.gbl. ..

"Jon Skeet [C# MVP]" <sk***@pobox.co mwrote in message
news:MP******** *************@m snews.microsoft .com...

RP <rp*********@gm ail.comwrote:
If an exception occurs, how to get the error number. I mean, is there
anything like ex.number?

For many exceptions there *isn't* an error number - after all, you can
create whatever exception you want and throw it.

heh. Perfectly valid, if not quite correct, code...

Object errorNumber = (object) 101;
throw errorNumber;

One day I'm going to figure out why any arbitrary thing can be thrown,
rather than constraining it to only Exceptions...

--
Chris Mullins

[Nicholas Paldino [.NET/C# MVP]]

Which is correct, but it doesn't validate Chris's post, which indicates
that you can actually throw something in C# which does not derive from
Exception.

You could do this in C++/CLI or in IL, but not in C#. And yes, you can
catch it with the catch block which doesn't have an exception argument.

I actually did some of the review work on that book, and know Mark, so I
know exactly which section you are referring to. =)

--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m

"Peter Bromberg [C# MVP]" <pb*******@yaho o.yohohhoandabo ttleofrum.comwr ote
in message news:51******** *************** ***********@mic rosoft.com...

According to Michaelis, "In C# 2.0, all exceptions, whether deriving from
System.Exceptio n or not, will propagate into C# assemblies as derived from
System.Exceptio n. .... the CIL code corresponding to an empty catch block
is,
in fact, a catch(object) block..."
-- Peter
Recursion: see Recursion
site: http://www.eggheadcafe.com
unBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder: http://www.blogmetafinder.com

"Nicholas Paldino [.NET/C# MVP]" wrote:

> Actually, it's not valid C# code. While the CLR does allow for
objects
to be thrown, in C#, the compiler requires that the target of the throw
statement derive from System.Exceptio n.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m
"Chris Mullins [MVP - C#]" <cm******@yahoo .comwrote in message
news:%2******* *********@TK2MS FTNGP02.phx.gbl ...

"Jon Skeet [C# MVP]" <sk***@pobox.co mwrote in message
news:MP******** *************@m snews.microsoft .com...
RP <rp*********@gm ail.comwrote:
If an exception occurs, how to get the error number. I mean, is there
anything like ex.number?

For many exceptions there *isn't* an error number - after all, you can
create whatever exception you want and throw it.

heh. Perfectly valid, if not quite correct, code...

Object errorNumber = (object) 101;
throw errorNumber;

One day I'm going to figure out why any arbitrary thing can be thrown,
rather than constraining it to only Exceptions...

--
Chris Mullins

[=?Utf-8?B?UGV0ZXIgQnJvbWJlcmcgW0MjIE1WUF0=?=]

Yep, you are correct -- in C# 2.0 Chris's example code is not valid - you
would get "type object does not extend System.Exceptio n" in Intellisense, and
a similar compiler error.

-- Peter
Recursion: see Recursion
site: http://www.eggheadcafe.com
unBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder: http://www.blogmetafinder.com

"Nicholas Paldino [.NET/C# MVP]" wrote:

Which is correct, but it doesn't validate Chris's post, which indicates
that you can actually throw something in C# which does not derive from
Exception.

You could do this in C++/CLI or in IL, but not in C#. And yes, you can
catch it with the catch block which doesn't have an exception argument.

I actually did some of the review work on that book, and know Mark, so I
know exactly which section you are referring to. =)

--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m

"Peter Bromberg [C# MVP]" <pb*******@yaho o.yohohhoandabo ttleofrum.comwr ote
in message news:51******** *************** ***********@mic rosoft.com...

According to Michaelis, "In C# 2.0, all exceptions, whether deriving from
System.Exceptio n or not, will propagate into C# assemblies as derived from
System.Exceptio n. .... the CIL code corresponding to an empty catch block
is,
in fact, a catch(object) block..."
-- Peter
Recursion: see Recursion
site: http://www.eggheadcafe.com
unBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder: http://www.blogmetafinder.com

"Nicholas Paldino [.NET/C# MVP]" wrote:

Actually, it's not valid C# code. While the CLR does allow for
objects
to be thrown, in C#, the compiler requires that the target of the throw
statement derive from System.Exceptio n.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m
"Chris Mullins [MVP - C#]" <cm******@yahoo .comwrote in message
news:%2******** ********@TK2MSF TNGP02.phx.gbl. ..
"Jon Skeet [C# MVP]" <sk***@pobox.co mwrote in message
news:MP******** *************@m snews.microsoft .com...
RP <rp*********@gm ail.comwrote:
If an exception occurs, how to get the error number. I mean, is there
anything like ex.number?

For many exceptions there *isn't* an error number - after all, you can
create whatever exception you want and throw it.

heh. Perfectly valid, if not quite correct, code...

Object errorNumber = (object) 101;
throw errorNumber;

One day I'm going to figure out why any arbitrary thing can be thrown,
rather than constraining it to only Exceptions...

--
Chris Mullins