Glad you were able to sort this out!
Cheers
On 2016-11-04 14:32, DaveS wrote:
Solved.
I had a reference to version 1.2.10 which was causing this version to be
loaded from the GAC.
--
View this message in context:
Solved.
I had a reference to version 1.2.10 which was causing this version to be
loaded from the GAC.
--
View this message in context:
http://apache-logging.6191.n7.nabble.com/Issue-with-Custom-Appender-tp70625p70639.html
Sent from the Log4net - Users mailing list archive at Nabble.com.
I am building the custom appender against:
log4net, Version=1.2.15.0, Culture=neutral, PublicKeyToken=669e0ddf0bb1aa2a
And this is the same DLL that is being loaded by the application.
I have uploaded the log file.
Dominik Psenner wrote
> Hi Dave,
>
> would you please send us a the complete
Hi Dave,
would you please send us a the complete log4net internal logs including
debug logs?
Anyway it smells like an issue with incompatible binaries. You could
check if both the log4net assembly that your custom appender was linked
against and the log4net assembly that your application
I have created a custom appender to work alongside two other appenders. The
problem I have having is that the custom appender isn't receiving any logs.
My custom appender simply inherits from AppenderSkeleton. However, I have
also tried creating my own appender that implements IAppender.
My
Hi Nicholas
On 2016-11-01, Nicholas Duane wrote:
> Got some questions around this. I was hoping that if I put the call
> to LogManager.Shutdown() in my application it might call Close() on
> all the appenders. However, that doesn't seem to be the case.
That's what I would have expected as
