[jira] [Comment Edited] (LOG4NET-504) Exception mode during configuration

["Gregory Zak (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4NET-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141873#comment-15141873 ] 

Gregory Zak edited comment on LOG4NET-504 at 2/10/16 10:47 PM:
---------------------------------------------------------------

No, the problem is that the app didn't have permissions to write the log files, including the internal logging files. In case of permission issues, it seems reasonable to throw exceptions to the user so they don't spend hours pulling their hair out wondering why on earth nothing is being written. After all, permission issues are something you solve once at the beginning and then everything is smooth afterwards.


was (Author: thegzak@gmail.com):
No, the problem is that the app didn't have permissions to write the log files, including the internal logging files. In case of permission issues, it seems reasonable to through exceptions to the user so they don't spend hours pulling their hair out wondering why on earth nothing is being written. After all, permission issues are something you solve once at the beginning and then everything is smooth afterwards.

> 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
>            Priority: Minor
>
> 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)