Closed torndar closed 9 years ago
And this all works if you set the appender-ref to RollingLogFileAppender? The stack trace is not showing any Log4Net.async methods in the stack trace.
Changing the config to what appears below results in a successful log file. One thing that might be an issue that I just thought of is that Log4Net.Aysnc nuget package was built against log4net 1.2.11 but I have 1.2.13 in the project with a binding redirect.
<appender name="asyncForwarder" type="Log4Net.Async.ParallelForwardingAppender,Log4Net.Async">
<!-- <appender-ref ref="RollingLogFileAppender" /> -->
</appender>
<root>
<level value="ALL" />
<appender-ref ref="RollingLogFileAppender" />
<!-- <appender-ref ref="asyncForwarder" /> -->
</root>
I'm on holiday at the moment but next week I will convert the solution over to Paket which uses proper sem ver (unlike the NuGet client) and I will float the version of log4net so it builds with the latest version. The unit tests should always pick up any breaking changes.
Just to clarify, will NuGet builds still be available after this conversion?
Yep! It will still publish a package to NuGet but the nuspec will be much better defined.
Is this still on your TODO list?
Sorry I completely forgot about this. I have just converted to Paket, pulled the latest log4net and published 1.3.0 to NuGet.
With log4net debugging enabled I get the log and error below on the console.
Config
log4net output