NLog vs .NET logging

[OliLogger]

Some javascript/style in this post has been disabled (why?)

Hi all, I've been evaluating NLog as a solution to a requirement I have for (not surprisingly) logging in a project which covers disparate components on numerous servers written in C++ and C# in EXEs and on websites.

 

Meanwhile my colleague was telling me about the built-in .NET framework logging, and it all sounds quite similar! The idea of logging to multiple sources, the routing of logs using a config file, filters etc. I think the Layout Renderers may be functionality beyond what .NET framework logging offers.

 

I'm aware that NLog offers a DLL version for C++ use and a COM interface. However, if I felt that .NET framework logging offered everything that NLog supplied except for those things, I would just build assemblies in C# which would offer COM and DLL interfaces (which I expect is what NLog has done).

 

So, what's the 'killer feature' which means I should use NLog rather than .NET framework logging? Talk me into it.

 

Any pro or con discussions gratefully received.

 

Thanks,

Oli

 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Nlog-list mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nlog-list

[Jay R. Wren-2]

My Advice to you:

Sell yourself on it. Try using this fictional built in .NET framework
logging. Then try nlog. Everyone has their own opinions, so maybe you
will like using this vapor built-in thing. But I know I prefer things
which work and are easy to use. NLog works and is easy to use.

You should ask your friend for more specifics. What namespace? What
assembly?
--
Jay

p.s. you may also consider new friends. j/k ;p

Oliver Seaman wrote:

> Hi all, I've been evaluating NLog as a solution to a requirement I
> have for (not surprisingly) logging in a project which covers
> disparate components on numerous servers written in C++ and C# in EXEs
> and on websites.
>  
> Meanwhile my colleague was telling me about the built-in .NET
> framework logging, and it all sounds quite similar! The idea of
> logging to multiple sources, the routing of logs using a config file,
> filters etc. I think the Layout Renderers may be functionality beyond
> what .NET framework logging offers.
>  
> I'm aware that NLog offers a DLL version for C++ use and a COM
> interface. However, if I felt that .NET framework logging offered
> everything that NLog supplied except for those things, I would just
> build assemblies in C# which would offer COM and DLL interfaces (which
> I expect is what NLog has done).
>  
> So, what's the 'killer feature' which means I should use NLog rather
> than .NET framework logging? Talk me into it.
>  
> Any pro or con discussions gratefully received.
>  
> Thanks,
> Oli
>  
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Nlog-list mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/nlog-list
>  

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Nlog-list mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nlog-list

[Mads Bondo Dydensborg]

onsdag 05 September 2007 skrev Oliver Seaman:

> Meanwhile my colleague was telling me about the built-in .NET framework
> logging, and it all sounds quite similar! The idea of logging to multiple
> sources, the routing of logs using a config file, filters etc. I think the
> Layout Renderers may be functionality beyond what .NET framework logging
> offers.    

What is the builtin .NET logging? As Jay wrote: pointers to docs appreciated.
Its a bit hard to discuss, if we do not know the other way.

NLog works really great. I work on a project that needs to work on both
Linux/Mono and Windows/MS. NLog just works - on both platforms.

We "sold" NLog to our windows developers in about 15 minutes.

Its been a great boon to us, that NLog is easily extensible. The config system
works like a charm, IMHO.

Regards,

Mads

--
Med venlig hilsen/Regards

Systemudvikler/Systemsdeveloper cand.scient.dat, Ph.d., Mads Bondo Dydensborg
Dansk BiblioteksCenter A/S, Tempovej 7-11, 2750 Ballerup, Tlf. [phone]


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Nlog-list mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nlog-list

[Andrew Stone-2]

Hi Oli,

If by system.Diagnostics you mean "built in logging" you're in for a shock. ;)
Nlog is a fully featured logging component that is extremely flexible and extendable.

I have implemented NLog on several large corporate systems as well as mobile devices running the compact framework. You can be assured It's fast and reliable.
I have tried Log4Net, rolling my own with system.Diganostics, the Microsoft block and some others that were floating around a few years back.  

Since using NLog I have never looked back.

Hope this helps.

Stonie.

On 9/6/07, Mads Bondo Dydensborg <[hidden email]> wrote:

onsdag 05 September 2007 skrev Oliver Seaman:

> Meanwhile my colleague was telling me about the built-in .NET framework
> logging, and it all sounds quite similar! The idea of logging to multiple
> sources, the routing of logs using a config file, filters etc. I think the
> Layout Renderers may be functionality beyond what .NET framework logging
> offers.

What is the builtin .NET logging? As Jay wrote: pointers to docs appreciated.
Its a bit hard to discuss, if we do not know the other way.

NLog works really great. I work on a project that needs to work on both
Linux/Mono and Windows/MS. NLog just works - on both platforms.

We "sold" NLog to our windows developers in about 15 minutes.

Its been a great boon to us, that NLog is easily extensible. The config system
works like a charm, IMHO.

Regards,

Mads

--
Med venlig hilsen/Regards

Systemudvikler/Systemsdeveloper cand.scient.dat, Ph.d., Mads Bondo Dydensborg
Dansk BiblioteksCenter A/S, Tempovej 7-11, 2750 Ballerup, Tlf. [phone]


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>   http://get.splunk.com/
_______________________________________________
Nlog-list mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nlog-list

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Nlog-list mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nlog-list

[Brad Bruce-2]

Some javascript/style in this post has been disabled (why?)

Andrew Stone wrote:

Hi Oli,

If by system.Diagnostics you mean "built in logging" you're in for a shock. ;)
Nlog is a fully featured logging component that is extremely flexible and extendable.

I have implemented NLog on several large corporate systems as well as mobile devices running the compact framework. You can be assured It's fast and reliable.
I have tried Log4Net, rolling my own with system.Diganostics, the Microsoft block and some others that were floating around a few years back.  

Since using NLog I have never looked back.

Hope this helps.

Stonie.

On 9/6/07, Mads Bondo Dydensborg <[hidden email]> wrote:

onsdag 05 September 2007 skrev Oliver Seaman:

> Meanwhile my colleague was telling me about the built-in .NET framework
> logging, and it all sounds quite similar! The idea of logging to multiple
> sources, the routing of logs using a config file, filters etc. I think the
> Layout Renderers may be functionality beyond what .NET framework logging
> offers.

What is the builtin .NET logging? As Jay wrote: pointers to docs appreciated.
Its a bit hard to discuss, if we do not know the other way.

NLog works really great. I work on a project that needs to work on both
Linux/Mono and Windows/MS. NLog just works - on both platforms.

We "sold" NLog to our windows developers in about 15 minutes.

Its been a great boon to us, that NLog is easily extensible. The config system
works like a charm, IMHO.

Regards,

Mads

--
Med venlig hilsen/Regards

Systemudvikler/Systemsdeveloper cand.scient.dat, Ph.d., Mads Bondo Dydensborg
Dansk BiblioteksCenter A/S, Tempovej 7-11, 2750 Ballerup, Tlf. [phone]


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>   http://get.splunk.com/
_______________________________________________
Nlog-list mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nlog-list

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
  

_______________________________________________
Nlog-list mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nlog-list
  

The .NET logging isn't fictional.  It just isn't "in-the-box".  You have to install the Microsoft Enterprise Library and then you get the logging block.  It's what is used by the Patterns and Practices group in most of their projects.  That said... Something doesn't "feel" right about it.  I've been using NLog for a while (and not really using more than basic features) and I love it.  If I needed more runtime configuration for my logging, I might look closer at the logging block.  So far though even the basic functionality of NLog kicks the pants off of writing my own logging.

Brad Bruce
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Nlog-list mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nlog-list