Return-Path: 
 <log4net-user-return-3494-apmail-logging-log4net-user-archive=logging.apache.org@logging.apache.org>
Delivered-To: apmail-logging-log4net-user-archive@www.apache.org
Received: (qmail 69456 invoked from network); 7 Nov 2006 02:30:24 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 7 Nov 2006 02:30:24 -0000
Received: (qmail 18075 invoked by uid 500); 7 Nov 2006 02:30:34 -0000
Delivered-To: apmail-logging-log4net-user-archive@logging.apache.org
Received: (qmail 18051 invoked by uid 500); 7 Nov 2006 02:30:34 -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 18040 invoked by uid 99); 7 Nov 2006 02:30:34 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Nov 2006 18:30:34 -0800
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: local policy)
Received: from [198.102.62.103] (HELO esri3.esri.com) (198.102.62.103)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Nov 2006 18:30:20 -0800
Received: from hardwire.esri.com (hardwire.esri.com [10.49.4.180])
	by esri3.esri.com (8.11.6+Sun/8.11.6) with ESMTP id kA72Txg21299
	for <log4net-user@logging.apache.org>; Mon, 6 Nov 2006 18:29:59 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Possible To Name Log File After Assembly?
Date: Mon, 6 Nov 2006 18:29:58 -0800
Message-ID: <627102C921CD9745B070C3B10CB8199BCB6F36@hardwire.esri.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Possible To Name Log File After Assembly?
Thread-Index: AccCFKACRgYsIwo/ThO6kTY89D9jWw==
From: "Milad Ershaghi" <mershaghi@esri.com>
To: <log4net-user@logging.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org

Dear Community,

I was wondering if it is possible to name a log file after an assembly
via the config file. Here is my config file:

--

<?xml version=3D"1.0" encoding=3D"utf-8"?>
<configuration>
	<configSections>
		<section name=3D"log4net"
type=3D"System.Configuration.IgnoreSectionHandler"/>
	</configSections>
	<log4net>
		<root>
			<level value=3D"ALL"/>
			<appender-ref ref=3D"LogFileAppender"/>
		</root>
		<appender name=3D"LogFileAppender"
type=3D"log4net.Appender.FileAppender">
			<threshold value=3D"ALL"/>
			<file value=3D"log4net.log"/>
			<appendToFile value=3D"false"/>
			<immediateFlush value=3D"true"/>
			<lockingModel
type=3D"log4net.Appender.FileAppender+ExclusiveLock" />
			<layout type=3D"log4net.Layout.PatternLayout">
				<header value=3D"[Start of
Execution]&#13;&#10;"/>
				<footer value=3D"[End of
Execution]&#13;&#10;"/>
				<conversionPattern value=3D"%date
[%thread] %-5level %logger [%property{NDC}] - %message%newline"/>
			</layout>
		</appender>
  </log4net>
</configuration>

--

Would it be possible to replace "log4net.log" with some other parameter
that would refer to the assembly name say in braces and then add on a
file extension. For example:

<file value=3D"{AssemblyName}.log"/>

Or is there some other way to accomplish this?

Thanks

Sincerely,

Milad