Mailing-List: contact log4net-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4NET User" <log4net-user@logging.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Subject: RE: how often to call XmlConfigurator.Configure
Date: Fri, 3 Sep 2010 12:20:27 +0200
Message-ID: <0794C17B67A72245B24284103E4959D2315DBA@main.hasam.cz>
In-Reply-To: <755840.76737.qm@web56301.mail.re3.yahoo.com>
Thread-Topic: how often to call XmlConfigurator.Configure
Thread-Index: ActKwp5oFtUkIKYBQqWpzNbLqZLObgAjk2Sw
References: <755840.76737.qm@web56301.mail.re3.yahoo.com>
From: "Radovan Raszka" <raszka@hasam.cz>
To: "Log4NET User" <log4net-user@logging.apache.org>

Log4net system should be configured only once int the "starting"  class =
of your application (first class used in the application) or any other =
class but before first logging attempt..
If you configure more times, only the last configuration is used.
But you can use log4net in way that every class uses its own appender.
RR

-----P=F9vodn=ED zpr=E1va-----
Od: T Dog [mailto:acedog032000@yahoo.com]=20
Odesl=E1no: 2. z=E1=F8=ED 2010 19:16
Komu: log4net-user@logging.apache.org
P=F8edm=ECt: how often to call XmlConfigurator.Configure

I have a simple C# .net 2.0 program where a console application calls =
into a Caller class which then calls into a Callee class.=A0 I want to =
have separate log4net configurations for the console application, for =
the Caller dll, and for the Callee dll.=A0 Each of the 3 should write to =
its own rolling log file appender.=A0=A0 I call =
XmlConfigurator.Configure in the constructor of the Caller, the Callee, =
and in the Main method of the console application.=A0 It ends up that =
the console application starts writing to its own log file, but then =
ends up writing into the innermost, the Callee's, log file.=A0 I can get =
the console application to write back to its own log file if I call =
XmlConfigurator.Configure again before I want to write to the console =
app's log file.=A0 Is that necessary or did I configure this =
incorrectly?=A0 I want to be able to have varying levels of log4net =
capability and verbosity at each of the 3 levels.

Here's the guts of the console application:

=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
log4net.Config.XmlConfigurator.Configure(new =
System.IO.FileInfo(Assembly.GetExecutingAssembly().Location + =
".config"));

=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 string message =3D "message from main =
generated at : " + DateTime.Now.ToLongTimeString();
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 _log.Error("error" + message);
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 _log.Warn("warn" + message);
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 _log.Info("info" + message);
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 _log.Debug("debug" + message);
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=20
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Caller caller =3D new Caller();
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 caller.MethodOne();

=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 // if the following line is commented =
out, then the output goes into the Callee's log file (which was the last =
class to call XmlConfigurator.Configure), not into the console =
application's log file
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
log4net.Config.XmlConfigurator.Configure(new =
System.IO.FileInfo(Assembly.GetExecutingAssembly().Location + =
".config"));
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 message =3D "message from main generated =
at : " + DateTime.Now.ToLongTimeString();
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 _log.Error("error" + message);
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 _log.Warn("warn" + message);
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 _log.Info("info" + message);
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 _log.Debug("debug" + message);

=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Caller caller2 =3D new Caller();
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 caller2.MethodOne();


     =20