|
RemotingAppender: msg#00084log.log4net.user
I am using Log4NET 1.2 beta 8 in my application. I have a ASP.NET web site that communicates with the business logic on a back-end remote (app) server using .NET remoting. I use IIS6 to host my remote objects. The app server already uses Log4NET for logging. I have a very thin wrapper around Log4NET. I would like to use Log4NET to log statements from my ASP.NET site to the backend app server. I am thinking that the RemotingAppender would be what I should use. However, I am having some trouble setting it up. The examples in the Log4NET distribution seem to be if the .NET remoting host was a Windows service or console app. Has anybody used the RemotingAppender successfully with IIS6? Instead of using the RemotingAppender on the client side, I've also considered just creating a very simple proxy that has all the same Log4NET logging calls (Debug, Info, etc.). Then, on the server side I would pass the call on to Log4NET. This approach seems somewhat more straightforward to me, and I don't have to put Log4NET on the client as well (not that that is a big deal or anything really). Any recommendations/suggestions? Thanks! |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | RE: very simple question: 00084, Nicko Cadell |
|---|---|
| Next by Date: | Log4Net Viewer: 00084, Shaily Goel |
| Previous by Thread: | very simple questioni: 00084, Williams, Damon |
| Next by Thread: | Log4Net Viewer: 00084, Shaily Goel |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |