Return-Path: 
 <log4net-user-return-2152-apmail-logging-log4net-user-archive=logging.apache.org@logging.apache.org>
Delivered-To: apmail-logging-log4net-user-archive@www.apache.org
Received: (qmail 26557 invoked from network); 14 Aug 2005 21:07:36 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 14 Aug 2005 21:07:36 -0000
Received: (qmail 87126 invoked by uid 500); 14 Aug 2005 21:07:35 -0000
Delivered-To: apmail-logging-log4net-user-archive@logging.apache.org
Received: (qmail 87095 invoked by uid 500); 14 Aug 2005 21:07:35 -0000
Mailing-List: contact log4net-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:log4net-user-help@logging.apache.org>
list-unsubscribe: <mailto:log4net-user-unsubscribe@logging.apache.org>
List-Post: <mailto:log4net-user@logging.apache.org>
Reply-To: "Log4NET User" <log4net-user@logging.apache.org>
List-Id: <log4net-user.logging.apache.org>
Delivered-To: mailing list log4net-user@logging.apache.org
Received: (qmail 87082 invoked by uid 99); 14 Aug 2005 21:07:35 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Aug 2005 14:07:35 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of nicko@neoworks.com designates
 80.168.17.114 as permitted sender)
Received: from [80.168.17.114] (HELO kronos.neoworks.co.uk) (80.168.17.114)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Aug 2005 14:07:55 -0700
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Subject: RE: What is wrong with Log4Net web.config?
Date: Sun, 14 Aug 2005 22:09:08 +0100
Message-ID: <DDEB64C8619AC64DBC074208B046611C769404@kronos.neoworks.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: What is wrong with Log4Net web.config?
Thread-Index: AcWX2OrDr+BzjhjeRxGr7O2HRKPLlwJOoDfQ
From: "Nicko Cadell" <nicko@neoworks.com>
To: "Log4NET User" <log4net-user@logging.apache.org>,
	<911@learnasp.com>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Charles,

There are a couple of general points I want to bring up regarding your
example.

You should try to call DOMConfigurator.Configure() only once, and if
possible as soon as the application starts. Adding this code to your
Page_Load method is not best practice. The Application_Start method of
the Global.asax is a better place in a web app.

In your config file the <root> element is commented out. I would
recommend always having a <root> element that specifies an appender. I
know that in your case using a <logger> with the correct name has the
same effect, but if you are trying to show people the right way to do it
I would use the <root> element.

Cheers,
Nicko

> -----Original Message-----
> From: Charles Carroll [mailto:charlesmarkcarroll@gmail.com]=20
> Sent: 03 August 2005 04:09
> To: log4net-user@logging.apache.org
> Subject: What is wrong with Log4Net web.config?
>=20
> http://www.learnasp.com/freebook/learn/log4net1.aspx
>=20
> when we run that program it should output to trace.write the=20
> Log.Info statements.
>=20
>=20