You can use this configuration file (nlog.config in the app path):

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;
    &lt;nlog xmlns=&quot;http://www.nlog-project.org/schemas/NLog.xsd&quot;
          xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;&gt;
    
      &lt;targets&gt;
            &lt;target name=&quot;debugger&quot; xsi:type=&quot;Debugger&quot; layout=&quot;${logger}::${message}&quot;/&gt;
      &lt;/targets&gt;
    
      &lt;rules&gt;
        &lt;logger name=&quot;*&quot; minlevel=&quot;Trace&quot; writeTo=&quot;debugger&quot; /&gt;
      &lt;/rules&gt;
    &lt;/nlog&gt;

-Scott

I want to have a look at how Java implements LinkedList. Where should I go to look at the source code?

Where can I see the source code of the Sun JDK?

I have an application that I&#39;m trying to wrap into a jar for easier deployment.  The application compiles and runs fine (in a Windows cmd window) when run as a set of classes reachable from the CLASSPATH.  But when I jar up my classes and try to run it with java 1.6 in the same cmd window, I start getting exceptions:

    C:\dev\myapp\src\common\datagen&gt;C:/apps/jdk1.6.0_07/bin/java.exe -classpath C:\myapp\libs\commons -logging-1.1.jar -server -jar DataGen.jar
    Exception in thread &quot;main&quot; java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
        at com.example.myapp.fomc.common.datagen.DataGenerationTest.&lt;clinit&gt;(Unknown Source)
    Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory
        at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
        ... 1 more
        
The funny thing is, the offending LogFactory seems to be in commons-logging-1.1.jar, which is in the class path specified.  The jar file (yep, it&#39;s really there):

    C:\dev\myapp\src\common\datagen&gt;dir C:\myapp\libs\commons-logging-1.1.jar
     Volume in drive C is Local Disk
     Volume Serial Number is ECCD-A6A7

     Directory of C:\myapp\libs

    12/11/2007  11:46 AM            52,915 commons-logging-1.1.jar
               1 File(s)         52,915 bytes
               0 Dir(s)  10,956,947,456 bytes free

The contents of the commons-logging-1.1.jar file:

    C:\dev\myapp\src\common\datagen&gt;jar -tf C:\myapp\libs\commons-logging-1.1.jar
    META-INF/
    META-INF/MANIFEST.MF
    org/
    org/apache/
    org/apache/commons/
    org/apache/commons/logging/
    org/apache/commons/logging/impl/
    META-INF/LICENSE.txt
    META-INF/NOTICE.txt
    org/apache/commons/logging/Log.class
    org/apache/commons/logging/LogConfigurationException.class
    org/apache/commons/logging/LogFactory$1.class
    org/apache/commons/logging/LogFactory$2.class
    org/apache/commons/logging/LogFactory$3.class
    org/apache/commons/logging/LogFactory$4.class
    org/apache/commons/logging/LogFactory$5.class
    org/apache/commons/logging/LogFactory.class
    ... (more classes in commons-logging-1.1 ...)
    
Yep, commons-logging has the LogFactory class.  And finally, the contents of my jar&#39;s manifest:

    Manifest-Version: 1.0
    Ant-Version: Apache Ant 1.6.5
    Created-By: 10.0-b23 (Sun Microsystems Inc.)
    Main-Class: com.example.myapp.fomc.common.datagen.DataGenerationTest
    Class-Path: commons-logging-1.1.jar commons-lang.jar antlr.jar toplink
     .jar GroboTestingJUnit-1.2.1-core.jar junit.jar
     
This has stumped me, and any coworkers I&#39;ve bugged for more than a day now.  Just to cull the answers, for now at least, third party solutions to this are probably out due to licensing restrictions and company policies (e.g.: tools for creating exe&#39;s or packaging up jars).  The ultimate goal is to create a jar that can be copied from my development Windows box to a Linux server (with any dependent jars) and used to populate a database (so classpaths may wind up being different between development and deployment environments).  Any clues to this mystery would be greatly appreciated!

NoClassDefFoundError while trying to run my jar with java.exe -jar...what&#39;s wrong?

I&#39;m trying to send the output to the console (or colouredconsole) ... which I&#39;m hoping would (also?) go to the Visual Studio&#39;s `Output` window for any ASP.NET web site/app/mvc app. 

It doesn&#39;t by default, but if I change the target to &#39;file&#39; then it works for sure. 

Can NLog output to the `Output` window for web apps?

How can I output NLog messages to Visual Studio&#39;s Output Window?

I'm trying to send the output to the console (or colouredconsole) ... which I'm hoping would (also?) go to the Visual Studio's <code>Output</code> window for any ASP.NET web site/app/mvc app.
It doesn't by default, but if I change the target to 'file' then it works for sure.
Can NLog output to the <code>Output</code> window for web apps?

I&#39;m using jQuery to wire up some mouseover effects on elements that are inside an UpdatePanel. The events are bound in `$(document).ready` . For example:

    $(function() {    
        $(&#39;div._Foo&#39;).bind(&quot;mouseover&quot;, function(e) {
            // Do something exciting
        });    
    });

Of course, this works fine the first time the page is loaded, but when the UpdatePanel does a partial page update, it&#39;s not run and the mouseover effects don&#39;t work any more inside the UpdatePanel. 


What&#39;s the recommended approach for wiring stuff up in jQuery not only on the first page load, but every time an UpdatePanel fires a partial page update? Should I be using the ASP.NET ajax lifecycle instead of `$(document).ready`?

jQuery $(document).ready and UpdatePanels?

Which method is preferred?

    Session.Remove(&quot;foo&quot;);
    
    Session[&quot;foo&quot;] = null;

Is there a difference?

ASP.NET removing an item from Session?

I&#39;ve got a VS 2008 C# Web project and whenever I make some changes to the files in it (not even to the project file itself) VS will remove some lines like this from the csproj file:

    &lt;SubType&gt;ASPXCodeBehind&lt;/SubType&gt;

So something like this:

    &lt;Compile Include=&quot;Default.aspx.cs&quot;&gt;
      &lt;DependentUpon&gt;Default.aspx&lt;/DependentUpon&gt;
      &lt;SubType&gt;ASPXCodeBehind&lt;/SubType&gt;
    &lt;/Compile&gt;

will become

    &lt;Compile Include=&quot;Default.aspx.cs&quot;&gt;
      &lt;DependentUpon&gt;Default.aspx&lt;/DependentUpon&gt;
    &lt;/Compile&gt;

**BUT** the next time I work on this project it will add those lines back! It keeps going back and forth like this, resulting in a lot of meaningless &quot;changes&quot; in our source control system. This never used to happen with VS 2005 and it doesn&#39;t seem to be happening for other developers who work on the same project file, only for me.

Does anyone know why this is happening and how I can stop it from doing this?

VS 2008 keeps removing and re-adding &lt;SubType&gt;ASPXCodeBehind&lt;/SubType&gt;

I&#39;m looking for a lightweight, easy to setup CI server that I can run on my laptop along with Visual Studio &amp; Resharper. I&#39;m obviously looking at all the big names like CruiseControl, TeamCity etc etc but the biggest consideration to me is ease of setup and to a lesser extent memory footprint.

Edit: I&#39;d also like some suggestions for other solutions outside the big 2/3...

Edit: I&#39;m about to accept an answer if no one else has anything to add?




Best Continuous Integration Setup for a solo developer (.NET)

I need to search a string in the string array. I dont want to use any for looping in it

    string [] arr = {&quot;One&quot;,&quot;Two&quot;,&quot;Three&quot;};

    string theString = &quot;One&quot;

I need to check whether theString variable is present in arr.



How to search a string in String array

Anyone have experience for both?  How do they stack up against each other?

We are planning on using one of them for logging in an enterprise application.


References:

[log4net][1]

[nlog][2]


  [1]: http://logging.apache.org/log4net/index.html
  [2]: http://www.nlog-project.org/

EDIT: We have no existing dependencies to either nlog or log4net.

log4net vs. Nlog

My NLog targets is like this:

&lt;!-- language: xml --&gt;

    &lt;targets&gt;
      &lt;target xsi:type=&quot;Console&quot; name=&quot;console&quot; 
        layout=&quot;${longdate}|${level}|${message}&quot; /&gt;
      &lt;target xsi:type=&quot;File&quot; name=&quot;ErrorLog&quot; fileName=&quot;${basedir}/error.txt&quot;
              layout=&quot;${longdate}
              Trace: ${stacktrace} 
              ${message}&quot; /&gt;
      &lt;target xsi:type=&quot;File&quot; name=&quot;AccessLog&quot; fileName=&quot;${basedir}/access.txt&quot;
              layout=&quot;${shortdate} | ${message}&quot; /&gt;
    &lt;/targets&gt;

But this causes problems if the user isn&#39;t an admin on their machine, because they will not have write access to &quot;Program Files&quot;. How can I get something like `%AppData%` to NLog instead of BaseDir?

using AppData location in NLog

As per NLog&#39;s documentation:

&gt;Most applications will use one logger per class, where the name of the logger is the same as the name of the class.

This is the same way that log4net operates. Why is this a good practice?

Why do loggers recommend using a logger per class?

I am interested in learning more about how people inject logging with dependency injection platforms.  Although the links below and my examples refer to log4net and Unity, I am not necessarily going to use either of those.  For dependency injection/IOC, I will probably use MEF as that is the standard that the rest of the project (large) is settling on.

I am very new to dependency injection/ioc and am pretty new to C# and .NET (have written very little production code in C#/.NET after the past 10 years or so of VC6 and VB6).  I have done a lot of investigation into the various logging solutions that are out there, so I think that I have a decent handle on their feature sets.  I am just not familiar enough the with actual mechanics of getting one dependency injected (or, maybe more &quot;correctly&quot;, getting an abstracted version of one dependency injected).

I have seen other posts related to logging and/or dependency injection like:
https://stackoverflow.com/questions/522370/dependency-injection-and-logging-interfaces

https://stackoverflow.com/questions/576185/logging-best-practices

https://stackoverflow.com/questions/166438/what-would-a-log4net-wrapper-class-look-like

https://stackoverflow.com/questions/1320844/again-about-log4net-and-unity-ioc-config

My question does not have specifically to do with &quot;How to I inject logging platform xxx using ioc tool yyy?&quot;  Rather, I am interested in how people have handled wrapping the logging platform (as is often, but not always recommended) and configuration (i.e. app.config).  For example, using log4net as an example, I could configure (in app.config) a number of loggers and then get those loggers (without dependency injection) in the standard way of using code like this:

    private static readonly ILog logger = LogManager.GetLogger(MethodBase.GetCurrentMethod().DeclaringType);


Alternatively, if my logger is not named for a class, but rather, for a functional area, I could do this:

    private static readonly ILog logger = LogManager.GetLogger(&quot;Login&quot;);
    private static readonly ILog logger = LogManager.GetLogger(&quot;Query&quot;);
    private static readonly ILog logger = LogManager.GetLogger(&quot;Report&quot;);


So, I guess that my &quot;requirements&quot; would be something like this:

1.  I would like to insulate my product&#39;s source from a direct dependency on a logging platform.

2.  I would like to be able to resolve a specific named logger instance (probably sharing the same instance among all requesters of the same named instance) either directly or indirectly by some kind of dependency injection, probably MEF.

3.  I don&#39;t know if I would call this a hard requirement, but I would like the ability to get a named logger (different than the class logger) on demand.  For example, I might create a logger for my class based on the class name, but one method needs particulary heavy diagnostics that I would like to control separately.  In other words, I might want a single class to &quot;depend&quot; on two separate logger instances.

Let&#39;s start with number 1.  I have read a number of articles, primarily here on stackoverflow, about whether or not it is a good idea to wrap.  See the &quot;best practices&quot; link above and go to [jeffrey hantin][1]&#39;s comment for one view about why it is bad to wrap log4net.  If you did wrap (and if you could wrap effectively) would you wrap strictly for the purpose of injection/removal of direct depdency?  Or would you also try to abstract away some or all of the log4net app.config information?  

Let&#39;s say I want to use System.Diagnostics, I would probably want to implement an interface-based logger (maybe even using the &quot;common&quot; ILogger/ILog interface), probably based on TraceSource, so that I could inject it.  Would you implement the interface, say over TraceSource, and just use the System.Diagnostics app.config information as is?

Something like this:

    public class MyLogger : ILogger
    {
      private TraceSource ts;
      public MyLogger(string name)
      {
        ts = new TraceSource(name);
      }
    
      public void ILogger.Log(string msg)
      {
        ts.TraceEvent(msg);
      }
    }
And use it like this:

    private static readonly ILogger logger = new MyLogger(&quot;stackoverflow&quot;);
    logger.Info(&quot;Hello world!&quot;)

Moving on to number 2 ... How to resolve a particular named logger instance?  Should I just leverage the app.config information of the logging platform that I choose (i.e. resolve the loggers based on the naming scheme in the app.config)?  So, in the case of log4net, might I prefer to &quot;inject&quot; LogManager (note that I know this is not possible since it is a static object)?  I could wrap LogManager (call it MyLogManager), give it an ILogManager interface, and then resolve MyLogManager.ILogManager interface.  My other objects could have a depenency (Import in MEF parlance) on ILogManager (Export from the assembly where it is implemented).  Now I could have objects like this:

    public class MyClass
    {
      private ILogger logger;
      public MyClass([Import(typeof(ILogManager))] logManager)
      {
        logger = logManager.GetLogger(&quot;MyClass&quot;);
      }
    }

Any time ILogManager is called, it would directly delegate to log4net&#39;s LogManager.  Alternatively, could the wrapped LogManager take the ILogger instances that it gets based on the app.config and add them to the(a ?) MEF container by name.  Later, when a logger of the same name is requested, the wrapped LogManager is queried for that name.  If the ILogger is there, it is resolved that way.  If this is possible with MEF, is there any benefit do doing so?

In this case, really, only ILogManager is &quot;injected&quot; and it can hand out ILogger instances in the way that log4net normally does.  How does this type of injection (essentially of a factory) compare to injecting the named logger instances?  This does allow for more easy leveraging of log4net&#39;s (or other logging platform) app.config file.

I know that I can get named instances out of the MEF container like this:

    var container = new CompositionContainer(&lt;catalogs and other stuff&gt;);
    ILogger logger = container.GetExportedValue&lt;ILogger&gt;(&quot;ThisLogger&quot;);

But how do I get the named instances into the container?  I know about the attribute based model where I could have different implementations of ILogger, each of which is named (via a MEF attribute), but that doesn&#39;t really help me.  Is there a way to create something like an app.config (or a section therein) that would list the loggers (all of the same implementation) by name and that MEF could read?  Could/should there be a central &quot;manager&quot; (like MyLogManager) that resolves named loggers via the underlying app.config and then inserts the resolved logger into the MEF container?  This way it would be available to someone else that has access to the same MEF container (although without the MyLogManager&#39;s knowledge of how to use log4net&#39;s app.config information, it seems that the container would be unable to resolve any named loggers directly).

This has already gotten pretty long.  I hope it that it is coherent.  Please feel free to share any specific information about how you dependency injected a logging platform (we are most likely considering log4net, NLog, or something (hopefully thin) built on System.Diagnostics) into your application.  

Did you inject the &quot;manager&quot; and have it return logger instances?  

Did you add some of your own config information in your own config section or in your DI platform&#39;s config section to make it easier/possible to inject logger instances directly (i.e. make your dependencies be on ILogger rather than ILogManager).  

What about having a static or global container that has either the ILogManager interface in it or the set of named ILogger instances in it.  So, rather than injecting in the conventional sense (via constructor, property, or member data), the logging dependency is explicitly resolved on demand.  Is this a good or bad way to dependency inject.

I am marking this as a community wiki since it doesn&#39;t seem like a question with a definite answer.  If anyone feels otherwise, feel free to change it.

Thanks for any help!

  [1]: https://stackoverflow.com/users/55637/jeffrey-hantin






Dependency injection and named loggers

What should the expected overhead be for logging?
I have tried this example
  
&lt;!-- language: c# --&gt;

     private class Person
     {
        private static Logger logger = LogManager.GetCurrentClassLogger();
        public string Name { get; private set; }
        public Person(string name)
           {
               Name = name;
               logger.Info(&quot;New person created with name {0}&quot;, name);
           }
      }
    
      List&lt;Person&gt; people = new List&lt;Person&gt;();
      for (int i = 0; i &lt; MAXTEST; i++)
      {
          people.Add(new Person(i.ToString()));
      }

With MAXTEST values of 100,500,1000, 5000

Results in MAXTEST,noLogging, Logging

    100,  25ms, 186ms    
    500,  33ms, 812ms    
    1000, 33ms, 1554ms
    5000, 33ms, 7654ms

Granted one would probably never log this excessive amount, but it this the performance hit one would expect? 

I have also tried using the asyncwrapper in the config

&lt;!-- language: xml --&gt;

     &lt;target name=&quot;asyncFile&quot; xsi:type=&quot;AsyncWrapper&quot;&gt;
       &lt;target name=&quot;file&quot; xsi:type=&quot;File&quot; fileName=&quot;${basedir}/log.txt&quot; /&gt;
     &lt;/target&gt;


Content Type	Original Author	Original Content on Stackoverflow
Question	Pure.Krome	View Question on Stackoverflow
Solution 1 - asp.net	Scott P	View Answer on Stackoverflow

How can I output NLog messages to Visual Studio's Output Window?

asp.net Problem Overview

asp.net Solutions

Solution 1 - asp.net

NoClassDefFoundError while trying to run my jar with java.exe -jar...what's wrong?

Where can I see the source code of the Sun JDK?

Attributions