Hello I know this is extremely basic, I just want to make sure I got it right.

is:

try{}
catch{}

the same as

try{}
catch(System.Exception e){}

I mean if I am not using the reference to the exception then I should simply
use
catch{} ? or is catch(System.Exception){} somehow more restricted on what
it catches than simply catch{}?

Thanks in advance

JT.

"John" <John (AT) discussions (DOT) microsoft.com> wrote

restrictive. To find out why your try catch blocks should always use a
parameter of type Exception (or subclass thereof), I suggest you look into
the important properties shared by these classes, such as Message (a string
containing a readable description of the raised exception).

--
Peter [MVP Visual Developer]
Jack of all trades, master of none.

John,
In addition to the other comments.

For C# & VB.NET code both are the same, as both languages only support
throwing exceptions that inherit from System.Exception.

However! If you call another language that allows you to throw exceptions
that do not derive from System.Exception will cause the two statements to be
semantically different.

For details see:

http://msdn.microsoft.com/library/de...pspec_8_10.asp

Hope this helps
Jay

"John" <John (AT) discussions (DOT) microsoft.com> wrote

Thanks!

Very helpful

JT.

"Jay B. Harlow [MVP - Outlook]" wrote:

Actually I am glad I posted this on

"microsoft.public.dotnet.academic" and on:
"microsoft.public.dotnet.general"

as I now discovered I got the wrong answer on
"microsoft.public.dotnet.general"

check it out:

http://msdn.microsoft.com/newsgroups...=en-us&m=1&p=1

no, the reply to your thread is entirely correct in .net.general. if you
need more detailed information, have a read of jeffrey richters book -
applied framework programming

--
Regards,
Alvin Bruney - ASP.NET MVP

[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
Now available @ www.lulu.com/owc, Amazon.com etc
"John" <John (AT) discussions (DOT) microsoft.com> wrote