Is it good a approach to derive each exception from my base exception?

[Julia]

Hi I have a system which composed from 2 different components

1.MailSender

2.MailReciever

the Name of my system is JuliaSystem

I wonder if it is a good approach to derive all my custom exceptions from
JuliaSystemExce ption

and than declare a abase exception for each component?

for example for the mail sender I will have a base exception like the
following

MailSenderExcep tion:JuliaSyste mException

for specific exception of the mail sender I will do the following

FailedToConnect Exception:MailS enderException

Thanks.

[Bonj]

Why not just use one of the framework's inbuilt exceptions?

"Julia" wrote:

Hi I have a system which composed from 2 different components

1.MailSender

2.MailReciever

the Name of my system is JuliaSystem

I wonder if it is a good approach to derive all my custom exceptions from
JuliaSystemExce ption

and than declare a abase exception for each component?

for example for the mail sender I will have a base exception like the
following

MailSenderExcep tion:JuliaSyste mException

for specific exception of the mail sender I will do the following

FailedToConnect Exception:MailS enderException

Thanks.

[Julia]

Because i will be able to catch(if i want) all exceptions generated by my
system in a single place
and other in a second place
catch(JuliaSyst emException exception)
{
Log(e)
}
catch(System.Ex ception exception)
{
MessageBox(e.me ssage)
}

"Bonj" <Bo**@discussio ns.microsoft.co m> wrote in message
news:1D******** *************** ***********@mic rosoft.com...

Why not just use one of the framework's inbuilt exceptions?

"Julia" wrote:

Hi I have a system which composed from 2 different components

1.MailSender

2.MailReciever

the Name of my system is JuliaSystem

I wonder if it is a good approach to derive all my custom exceptions from JuliaSystemExce ption

and than declare a abase exception for each component?

for example for the mail sender I will have a base exception like the
following

MailSenderExcep tion:JuliaSyste mException

for specific exception of the mail sender I will do the following

FailedToConnect Exception:MailS enderException

Thanks.

[Dennis Myrén]

Then, it is probably a good approach.

--
Regards,
Dennis JD Myrén
Oslo Kodebureau
"Julia" <co********@012 .net.il> wrote in message
news:u6******** ******@TK2MSFTN GP14.phx.gbl...

Because i will be able to catch(if i want) all exceptions generated by my
system in a single place
and other in a second place
catch(JuliaSyst emException exception)
{
Log(e)
}
catch(System.Ex ception exception)
{
MessageBox(e.me ssage)
}

"Bonj" <Bo**@discussio ns.microsoft.co m> wrote in message
news:1D******** *************** ***********@mic rosoft.com...

Why not just use one of the framework's inbuilt exceptions?

"Julia" wrote:

>
> Hi I have a system which composed from 2 different components
>
> 1.MailSender
>
> 2.MailReciever
>
>
>
> the Name of my system is JuliaSystem
>
> I wonder if it is a good approach to derive all my custom exceptions from > JuliaSystemExce ption
>
> and than declare a abase exception for each component?
>
> for example for the mail sender I will have a base exception like the
> following
>
> MailSenderExcep tion:JuliaSyste mException
>
> for specific exception of the mail sender I will do the following
>
> FailedToConnect Exception:MailS enderException
>
>
>
>
>
> Thanks.
>
>
>

[Julia]

Thanks,
What about serialization, can I serialize an exception including all sub
inner exceptions?
I read some articles regarding permissions and security but I am not sure I
understood
what they talk about

Thanks

"Dennis Myrén" <de****@oslokb. no> wrote in message
news:WD******** **********@news 4.e.nsc.no...

Then, it is probably a good approach.

--
Regards,
Dennis JD Myrén
Oslo Kodebureau
"Julia" <co********@012 .net.il> wrote in message
news:u6******** ******@TK2MSFTN GP14.phx.gbl...

Because i will be able to catch(if i want) all exceptions generated by my system in a single place
and other in a second place
catch(JuliaSyst emException exception)
{
Log(e)
}
catch(System.Ex ception exception)
{
MessageBox(e.me ssage)
}

"Bonj" <Bo**@discussio ns.microsoft.co m> wrote in message
news:1D******** *************** ***********@mic rosoft.com...

Why not just use one of the framework's inbuilt exceptions?

"Julia" wrote:

>
> Hi I have a system which composed from 2 different components
>
> 1.MailSender
>
> 2.MailReciever
>
>
>
> the Name of my system is JuliaSystem
>
> I wonder if it is a good approach to derive all my custom exceptions

from

> JuliaSystemExce ption
>
> and than declare a abase exception for each component?
>
> for example for the mail sender I will have a base exception like the
> following
>
> MailSenderExcep tion:JuliaSyste mException
>
> for specific exception of the mail sender I will do the following
>
> FailedToConnect Exception:MailS enderException
>
>
>
>
>
> Thanks.
>
>
>

[Richard Blewett [DevelopMentor]]

This will allow you to handle your custom exceptions globally while not handling other system ones or other application ones that other components may throw application exceptions. If you want common data and facilities to be available in your application ceptions this is also a good idea. If you don't require either of these it doesn't really gain you anything (although its not a coist either apart from the extra source code you have to test and maintain).

Regards

Richard Blewett - DevelopMentor
http://staff.develop.com/richardb/weblog
Hi I have a system which composed from 2 different components

1.MailSender

2.MailReciever

the Name of my system is JuliaSystem

I wonder if it is a good approach to derive all my custom exceptions from
JuliaSystemExce ption

and than declare a abase exception for each component?

for example for the mail sender I will have a base exception like the
following

MailSenderExcep tion:JuliaSyste mException

for specific exception of the mail sender I will do the following

FailedToConnect Exception:MailS enderException

[Dennis Myrén]

Yes, you should be able to do that.

System.Exceptio n is marked as Serializable, and it implements ISerializable.

You can use GetObjectData to serialize the Exception.

You can use the protected constructor with the signature:
protected Exception(Seria lizationInfo info, StreamingContex t context)
to deserialize the Exception object.

You should also be able to serialize/deserialize using something like these
simple functions:
//
// public static void Serialize ( object instance, string filename )
// {
// Stream s = new FileStream(file name, FileMode.Create , FileAccess.Writ e);
// new System.Runtime. Serialization.F ormatters.Binar y.BinaryFormatt er()
// .Serialize(s, instance);
// s.Close();
// }
//
// public static object Deserialize ( string filename )
// {
// Stream s = new FileStream(file name, FileMode.Open);
// object o = new
System.Runtime. Serialization.F ormatters.Binar y.BinaryFormatt er()
// .Deserialize(s) ;
// s.Close();
// return o;
// }

--
Regards,
Dennis JD Myrén
Oslo Kodebureau
"Julia" <co********@012 .net.il> wrote in message
news:eW******** ******@TK2MSFTN GP12.phx.gbl...

Thanks,
What about serialization, can I serialize an exception including all sub
inner exceptions?
I read some articles regarding permissions and security but I am not sure
I
understood
what they talk about

Thanks

"Dennis Myrén" <de****@oslokb. no> wrote in message
news:WD******** **********@news 4.e.nsc.no...

Then, it is probably a good approach.

--
Regards,
Dennis JD Myrén
Oslo Kodebureau
"Julia" <co********@012 .net.il> wrote in message
news:u6******** ******@TK2MSFTN GP14.phx.gbl...

> Because i will be able to catch(if i want) all exceptions generated by my > system in a single place
> and other in a second place
>
>
> catch(JuliaSyst emException exception)
> {
> Log(e)
> }
> catch(System.Ex ception exception)
> {
> MessageBox(e.me ssage)
> }
>
>
>
> "Bonj" <Bo**@discussio ns.microsoft.co m> wrote in message
> news:1D******** *************** ***********@mic rosoft.com...
>> Why not just use one of the framework's inbuilt exceptions?
>>
>> "Julia" wrote:
>>
>> >
>> > Hi I have a system which composed from 2 different components
>> >
>> > 1.MailSender
>> >
>> > 2.MailReciever
>> >
>> >
>> >
>> > the Name of my system is JuliaSystem
>> >
>> > I wonder if it is a good approach to derive all my custom exceptions
> from
>> > JuliaSystemExce ption
>> >
>> > and than declare a abase exception for each component?
>> >
>> > for example for the mail sender I will have a base exception like
>> > the
>> > following
>> >
>> > MailSenderExcep tion:JuliaSyste mException
>> >
>> > for specific exception of the mail sender I will do the following
>> >
>> > FailedToConnect Exception:MailS enderException
>> >
>> >
>> >
>> >
>> >
>> > Thanks.
>> >
>> >
>> >
>
>

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

Hi,

Take a look at this thread:
http://groups.google.com/groups?hl=e...ublic.dotnet.*

You will find there a couple of good links, especially this
http://blogs.msdn.com/brada/archive/.../25/96251.aspx

in short it recommend that you keep your exception hierarchy wide and not
deep, a very interesting reading.
Cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"Julia" <co********@012 .net.il> wrote in message
news:eM******** ******@TK2MSFTN GP15.phx.gbl...

Hi I have a system which composed from 2 different components

1.MailSender

2.MailReciever

the Name of my system is JuliaSystem

I wonder if it is a good approach to derive all my custom exceptions from
JuliaSystemExce ption

and than declare a abase exception for each component?

for example for the mail sender I will have a base exception like the
following

MailSenderExcep tion:JuliaSyste mException

for specific exception of the mail sender I will do the following

FailedToConnect Exception:MailS enderException

Thanks.