> No and Yes. We've got the RemotingAppender working fine in a > few other applications now.
Humm. > I understand if you can't support > what we're trying to do with log4net and this VB6 wrapper, I don't understand why it wouldn't work through a COM wrapper. > but could you explain why the exception we're seeing mentions > a callback? Why would the RemotingAppender need a callback? If you mean RemotingAppender.SendBufferCallback that is used in the appender to make the remoting call from a thread pool thread rather than from your application calling thread. This is done to work around an issue with the application's CallContext getting cleared if there is an error in the remoting call. > Isn't it fire&forget to the remote Plugin? Sort of. The client does not depend on a value passed back or anything, but any unhandled exception on the server side is passed back and logged, so the remoting call is made synchronously. As this synchronous call is made asynchronously from a thread pool thread on the client this does not block the calling application. Nicko
