Details
-
Wish
-
Status: Closed
-
Minor
-
Resolution: Won't Fix
-
None
-
None
-
None
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 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!