EventLog writing etiquette

hello all,

i'm looking for some best (or acceptable) practice
guidelines for writing to
the event log.

how should my application behave if the event log is full
and is unable to
write to the log?

should i not allow the user to continue using the
application until it is
able to write to the log?
....should i let the user continue and just no longer write
to the log?...

or is this one of those "it depends"
questions...based on the "mission
critical-ness" of the application?
i couldn't find anything on the MS site about correct event
log writing
behaviour...only "how to write to the event log"

just looking for ideas and discussion....
Phil

--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.4.5/322 - Release
Date: 4/22/2006

Make sure you test this on Vista. My Event Log routine that
works on XP
fails on Vista due to the tightened security.

--------------------
“The final goal of the revolution is to create global
Islamic rule and a
regime of law to be led by the Imam Mahdi”. - commandant of
Iran’s elite
Islamic Revolutionary Guards Corps, Major General Yahya
Rahim Safavi
 

> -----Original Message-----
> From: Discussion forum for developers using Windows
Forms to 
> build apps and controls 
> [mailtoOTNET-WI
NFORMSDISCUSS.DEVELOP.COM] On Behalf Of Phil Sayers
> Sent: Monday, April 24, 2006 8:38 AM
> To: DOTNET-WINFORMSDISCUSS.DEVELOP.COM
> Subject: [DOTNET-WINFORMS] EventLog writing etiquette
> 
> hello all,
> 
> i'm looking for some best (or acceptable) practice
guidelines 
> for writing to the event log.
> 
> how should my application behave if the event log is
full and 
> is unable to write to the log?
> 
> should i not allow the user to continue using the
application 
> until it is able to write to the log?
> ....should i let the user continue and just no longer
write 
> to the log?...
> 
> or is this one of those "it depends"
questions...based on the 
> "mission critical-ness" of the application?
> i couldn't find anything on the MS site about correct
event 
> log writing behaviour...only "how to write to the
event log"
> 
> just looking for ideas and discussion....
> Phil
> 
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.385 / Virus Database: 268.4.5/322 -
Release 
> Date: 4/22/2006