My appreciation for your great work.
Regards
Kapil Sachdeva
http://www.dotnetcard.com/blogs/ksachdeva
----- Original Message ----- From: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>
To: "Log4NET User" <[email protected]>
Sent: Saturday, January 29, 2005 2:35 PM
Subject: Re: FileAppender & RemoteLoggingServerPlugin
Hi Kapil,
Regarding your question: "what do I lose if I switch to NLog?". I believe - not much.
Features?
Some things from log4net are deliberately not supported in NLog, but the logging interface and most standard features should be compatible. NLog is MUCH more simple than log4net as far as configuration is concerned. See the website for more information. The main design goal behind NLog is: typical logging scenarios (80%) should be easy, the rest (20%) should be possible.
Stability & maturity?
It's pretty stable, but not v1.0 yet, but I've been successfully using it in 4 commercial products and had only one serious bug till now (fixed a long time ago).
I'll be releasing a v0.5 release very soon (basically updated documentation & a new website (preview at http://nlog.sf.net/test/). Note that I want the core (log routing rules) to remain minimal and future additions will focus on adding new appenders/layout appenders/filters and providing documentation for them. v1.0 should provide an appender portfolio that's comparable with log4net and full documentation.
Robustness?
Basically should be the same as log4net. NLog will never break your program even if logging fails. NLog doesn't guarantee that logging messages will ever be written (same as log4net), but strives to do its best to achieve it. I don't need much more.
Ease of use?
In NLog configuration file you can say (which solves your problem):
<nlog>
<appenders>
<appender name="perThreadLogFile" type="File" fileName="${basedir}/logfile.${threadid}.log" />
</appenders>
<rules> <logger name="*" minLevel="Debug" appendTo="perThreadLogFile" /> </rules> </nlog>
Each thread will use a separate log file this way. Cool, isn't it ?
(if you're interested in future NLog developments, join nlog-list at http://lists.sourceforge.net/lists/listinfo/nlog-list)
Jarek
----- Original Message ----- From: "Ron Grabowski" <[EMAIL PROTECTED]>
To: "Log4NET User" <[email protected]>
Sent: Saturday, January 29, 2005 8:01 AM
Subject: Re: FileAppender & RemoteLoggingServerPlugin
Jaroslaw Kowalski (the author of NLog) would be a better person to ask. I believe he is subscribed to this list. He answers questions posted on the NLog mailing list. It looks like version 0.2 is still on Sourceforge. I believe 0.5 is now the stable version.
--- Kapil Sachdeva <[EMAIL PROTECTED]> wrote:
Thanks Ron,
keepFileOpen seems to be a really good idea in NLog. I did not know before your mail about NLog.
What do I loose if I switch to NLog from log4net in terms of functionality and robustness.
Regards & thanks again
Kapil Sachdeva
http://www.dotnetcard.com/blogs/ksachdeva
----- Original Message ----- From: "Ron Grabowski" <[EMAIL PROTECTED]>
To: "Log4NET User" <[email protected]>; "Kapil
Sachdeva"
<[EMAIL PROTECTED]>
Sent: Friday, January 28, 2005 3:49 PM
Subject: Re: FileAppender & RemoteLoggingServerPlugin
> 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
