NLog: http://nlog.sourceforge.net/
has a "keepFileOpen" property on its FileAppender that may do what you need: http://nlog.sourceforge.net/appenders.html#FileAppender NLog has almost identical method signatures to log4net. The switch shouldn't be terrible difficult (especially if your project includes its own ILog interface). - Ron --- Kapil Sachdeva <[EMAIL PROTECTED]> wrote: > Well Nicko isn't it little bit of tough sell if I am going to use the > stuff > in commerical product and have one application (Windows/NT service) > always > running so in case logging is enabled > this app may receive the log ? ............ Speaking of myself only, > I am > not comfortable with this setup. > > Can you suggest any other way ? .... I was thinking may be to write > my own > appender mostly like FileAppender (basically inheriting it like > RollingFileAppender) and in this appender > I read the name of file (lets say "mylog.txt") from the configuration > but > create a file by the name of mylog_ProcessID.txt. I do not have a > requirement that all processes should log to the > same file. > > May be you can suggest more elegant way of doing this !!. > > Regards & thanks > > Kapil Sachdeva > http://www.dotnetcard.com/blogs/ksachdeva > ----- Original Message ----- > From: "Nicko Cadell" <[EMAIL PROTECTED]> > To: "Log4NET User" <[email protected]> > Sent: Friday, January 28, 2005 3:25 PM > Subject: RE: FileAppender & RemoteLoggingServerPlugin > > > > > As we all know that FileAppender locks the file when logging > > is ON and another process can not acquire handle of the file. > > You recommend solution to it by using > > RemoteLogginServerPlugin. My understanding for this is that > > you will have deploy a remoting server application (which is > > always running) to do this. > > That is correct. > > > > > Please correct me if I am not clear about RemoteLogginServerPlugin. > > > > > > Kapil Sachdeva > > http://www.dotnetcard.com/blogs/ksachdeva > > > >
