duh, yup original poster said that.
-----Original Message-----
From: Discussion of development on the .NET platform using
any managed
language [mailto OTNET-CL
R DISCUSS.DEVELOP.COM]On Behalf Of Ivanoff,
Alex
Sent: Tuesday, August 29, 2006 12:57 PM
To: DOTNET-CLRDISCUSS.DEVELOP.COM
Subject: Re: [DOTNET-CLR] Where do you write your error when
all else
fails ?
You should not. It is a windows service.
-----Original Message-----
From: Discussion of development on the .NET platform using
any managed
language [mailtoOTNET-CL
RDISCUSS.DEVELOP.COM] On Behalf Of Greg Robinson
Sent: Tuesday, August 29, 2006 11:51
To: DOTNET-CLRDISCUSS.DEVELOP.COM
Subject: Re: [DOTNET-CLR] Where do you write your error when
all else fails
?
+1
You could also dialog the user, let them know the error
could not be logged
and ask them to print it and fax it or something similar.
-----Original Message-----
From: Discussion of development on the .NET platform using
any managed
language [mailtoOTNET-CL
RDISCUSS.DEVELOP.COM]On Behalf Of Bradley, Peter
Sent: Tuesday, August 29, 2006 12:45 PM
To: DOTNET-CLRDISCUSS.DEVELOP.COM
Subject: Re: [DOTNET-CLR] Where do you write your error when
all else fails
?
Or both. But seriously, you have to stop somewhere. I'm
all for careful
error checking, but it's a good idea to have some sort of a
view on whether
the extra steps are worth it.
If the database write fails AND the application log write
fails, for
example, I would guess that it's pretty clear that
someone's either changed
the identity the service is running under or the permissions
of that
identity. I'm not sure the data written to a file or email
is going to tell
you much more (and it may fail for the same reasons the
other failed,
anyway).
Don't let me put you off: but just consider whether it's
worth it or not.
If it is, then do it; of course.
Peter
-----Original Message-----
From: Discussion of development on the .NET platform using
any managed
language [mailtoOTNET-CL
RDISCUSS.DEVELOP.COM] On Behalf Of Greg Robinson
Sent: 29 August 2006 17:37
To: DOTNET-CLRDISCUSS.DEVELOP.COM
Subject: Re: [DOTNET-CLR] Where do you write your error when
all else fails
?
Text file and\or you can auto email it, which is what we
do.
-----Original Message-----
From: Discussion of development on the .NET platform using
any managed
language [mailtoOTNET-CL
RDISCUSS.DEVELOP.COM]On Behalf Of Steve W
Sent: Tuesday, August 29, 2006 12:30 PM
To: DOTNET-CLRDISCUSS.DEVELOP.COM
Subject: [DOTNET-CLR] Where do you write your error when all
else fails ?
I have an error handling mechanism in a windows service that
does this :
1. Try and write error to db - catch any exception raised
2. If exception
raised try and write to application log
If 2 raises an exception where should I try and write the
error information
next ?
I was thinking of a text file in the user's temporary
directory - does
anyone have any better suggestions ?
Thanks
Steve
===================================
This list is hosted by DevelopMentor. http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
===================================
This list is hosted by DevelopMentor(r) http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
===================================
This list is hosted by DevelopMentor. http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
===================================
This list is hosted by DevelopMentor. http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
===================================
This list is hosted by DevelopMentor. http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
===================================
This list is hosted by DevelopMentorŪ http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
|