; >> NC> system. If there is a problem logging log4net will not
> propagate
> >> errors
> >> NC> into the calling application.
> >> NC> While the current internal error handling is not flexible
> enough
> >> it is
> >> NC> un
ropagate
>> errors
>> NC> into the calling application.
>> NC> While the current internal error handling is not flexible enough
>> it is
>> NC> unlikely that it will be changed to accommodate a completely
>> reliable
>> NC> logging scenario.
---
> >> From: unegov [mailto:[EMAIL PROTECTED]
> >> Sent: 30 March 2006 08:43
> >> To: [email protected]
> >> Subject: Logging of the errors in logging
> >>
> >> Log4net is a great tool but I'm not fully satisfied how
&g
; Sent: 30 March 2006 08:43
>> To: [email protected]
>> Subject: Logging of the errors in logging
>>
>> Log4net is a great tool but I'm not fully satisfied how
>> log4net deals with errors in logging. In my project it is
>> necessary not to
completely reliable
logging scenario.
Regards,
Nicko
> -Original Message-
> From: unegov [mailto:[EMAIL PROTECTED]
> Sent: 30 March 2006 08:43
> To: [email protected]
> Subject: Logging of the errors in logging
>
> Log4net is a great tool but I'
Log4net is a great tool but I'm not fully satisfied how log4net deals
with errors in logging. In my project it is necessary not to lose any
logging messages if the logging is on so I would prefer log4net
threw exceptions rather than wrote errors of logging into
Console.Error and Trace as informatio
