You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "Gregory Zak (JIRA)" <ji...@apache.org> on 2016/02/02 00:25:40 UTC
[jira] [Updated] (LOG4NET-504) Exception mode during configuration
[ https://issues.apache.org/jira/browse/LOG4NET-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Zak updated LOG4NET-504:
--------------------------------
Description:
When getting started with log4net configuration for the first time, it would be extremely helpful to have a mode where a call to one of the various .Configure() methods would throw exceptions as they were encountered, rather than silently sailing past them / aborting.
I'm currently absolutely stuck with [this issue|http://stackoverflow.com/questions/35103249/log4net-not-writing-to-log-file] on stackoverflow, and I've already tried all the expected suggestions (enable trace debugging, check for config errors explicitly, etc etc), but I'm still staring at a silent failure (the most frustrating kind of failure) unable to make any progress.
Don't make me switch to NLog guys!
was:
When getting started with log4net configuration for the first time, it would be extremely helpful to have a mode where a call to one of the various .Configure() methods would throw exceptions as they were encountered, rather than silently sailing past them / aborting.
I'm currently absolutely stuck with the following issue on stackoverflow, and I've already tried all the expected suggestions (enable trace debugging, check for config errors explicitly, etc etc), but I'm still staring at a silent failure (the most frustrating kind of failure) unable to make any progress.
Don't make me switch to NLog guys!
> Exception mode during configuration
> -----------------------------------
>
> Key: LOG4NET-504
> URL: https://issues.apache.org/jira/browse/LOG4NET-504
> Project: Log4net
> Issue Type: Wish
> Components: Other
> Reporter: Gregory Zak
>
> When getting started with log4net configuration for the first time, it would be extremely helpful to have a mode where a call to one of the various .Configure() methods would throw exceptions as they were encountered, rather than silently sailing past them / aborting.
> I'm currently absolutely stuck with [this issue|http://stackoverflow.com/questions/35103249/log4net-not-writing-to-log-file] on stackoverflow, and I've already tried all the expected suggestions (enable trace debugging, check for config errors explicitly, etc etc), but I'm still staring at a silent failure (the most frustrating kind of failure) unable to make any progress.
> Don't make me switch to NLog guys!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)