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 (athena.apache.org: domain of mike.schall@gmail.com
 designates 209.85.221.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=KaclCS8xG3qWFe76OEo2YR0LMs+fXlbk+xL21UpzTkLzJgY0J6d6JaUOPEjo+JKXWw
         HBMyqqaN915vK7grh+suMW4+k7nNxTxnNP0TtEL25g9Auu882mrT+hieYBTeoJsa8hf7
         Vyy6x3maGpZ+sJOS4/x42Zg0R0/KXn6ALlEBw=
MIME-Version: 1.0
In-Reply-To: <25258147.post@talk.nabble.com>
References: <24807634.post@talk.nabble.com> <25253548.post@talk.nabble.com>
	 <5f9068320909020639j17cdb6eage9732d6d8825126e@mail.gmail.com>
	 <25258147.post@talk.nabble.com>
Date: Wed, 2 Sep 2009 10:25:31 -0500
Message-ID: <5f9068320909020825r9cc4c98mc12be8447d29b286@mail.gmail.com>
Subject: Re: Log in more than 1 log destination for different assemblies.
From: Michael Schall <mike.schall@gmail.com>
To: Log4NET User <log4net-user@logging.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Instead of using the GlobalContext.Properties to define where your
logs are coming from I would define a Shared/Static logger per class
based on the fully qualified class name allowing you to use the
logger hierarchy as defined here
http://logging.apache.org/log4net/release/manual/introduction.html

The FAQ has a section too...
http://logging.apache.org/log4net/release/faq.html#Implementing%20Logging

This way you can turn off specific loggers, direct them to different
appenders, ...

Mike

On Wed, Sep 2, 2009 at 9:01 AM, mattyboy<mattm@spdprintsolutions.com> wrote=
:
>
> Thanks for the replying.
>
> When I say mutliple assemblies I have a GUI app. and it uses log4net to l=
og
> to a file let's say 'C:\Claymore.log'.
>
> I have developed several .dll files which I call from within the GUI app.=
 =A0I
> want the code within the .dll files to also log to 'C:\Calymore.log'.
>
> I've actually just managed to get it working but I'm not using locking an=
d
> wonder whether I should be or not for this scenario. =A0As far as I'm awa=
re
> everything will run in the same process and should be fine without
> locking......?
>
> Here's what I've done:
>
> In both the GUI front-end and each .dll I have added the following entry =
to
> the AssemblyInfo.vb (yes, I'm using vb.net!) file
>
> <Assembly:
> log4net.Config.XMLConfigurator(ConfigFile:=3D"Claymore.exe.log4net",
> Watch:=3DTrue)>
>
> In GUI Front-End Assembly ONLY I've added 'Claymore.exe.log4net' file.
>
> Then in GUI Front-End class:
>
> Public Class frmDashboard
> =A0 =A0Public Shared logger As log4net.ILog
>
> =A0 =A0Private Sub frmDashboard_Load(ByVal sender As Object, ByVal e As
> System.EventArgs) Handles Me.Load
> =A0 =A0 =A0 =A0log4net.GlobalContext.Properties("AssemblyName") =3D
> Assembly.GetExecutingAssembly.GetName.Name()
> =A0 =A0 =A0 =A0logger =3D log4net.LogManager.GetLogger("ClaymoreLogger")
> =A0 =A0 =A0 =A0logger.Info("Dashboard_Load() - Start")
> =A0 =A0 =A0 =A0logger.Debug("Dashboard_Load() - Finish")
> =A0 =A0 =A0 =A0Dim clsGUI As New ClaymoreGUI.clsDashboard()
> =A0 =A0End Sub
> End Class
>
> In my ClaymoreGUI.dll:
>
> Public Class clsDashboard
> =A0 =A0Public Shared logger As log4net.ILog
>
> =A0 =A0Public Sub New()
> =A0 =A0 =A0 =A0log4net.GlobalContext.Properties("AssemblyName") =3D
> Assembly.GetExecutingAssembly.GetName.Name()
> =A0 =A0 =A0 =A0logger =3D log4net.LogManager.GetLogger("ClaymoreLogger")
> =A0 =A0 =A0 =A0logger.Info("New() - Start")
> =A0 =A0 =A0 =A0logger.Debug("New() - Finish")
> =A0 =A0End Sub
> End Class
>
> Seems to work well :-)
>
>
>
> Michael Schall wrote:
>>
>> When you say multiple assemblies, I assume you mean multiple
>> processes? =A0Logging this way is not suggested as for each log message
>> you have to reopen the file. =A0If you have really light logging, it
>> would probably be ok...
>>
>> Look at the LockingModel:
>> http://logging.apache.org/log4net/release/sdk/log4net.Appender.FileAppen=
der.LockingModel.html
>>
>> From http://logging.apache.org/log4net/release/config-examples.html:
>>
>> This example shows how to configure the appender to use the minimal
>> locking model that allows multiple processes to write to the same
>> file.
>>
>> <appender name=3D"FileAppender" type=3D"log4net.Appender.FileAppender">
>> =A0 =A0 <file value=3D"${TMP}\log-file.txt" />
>> =A0 =A0 <appendToFile value=3D"true" />
>> =A0 =A0 <lockingModel type=3D"log4net.Appender.FileAppender+MinimalLock"=
 />
>> =A0 =A0 <layout type=3D"log4net.Layout.PatternLayout">
>> =A0 =A0 =A0 =A0 <conversionPattern value=3D"%date [%thread] %-5level %lo=
gger
>> [%property{NDC}] - %message%newline" />
>> =A0 =A0 </layout>
>> </appender>
>>
>> On Wed, Sep 2, 2009 at 3:28 AM, mattyboy<mattm@spdprintsolutions.com>
>> wrote:
>>>
>>> Hi Christian,
>>>
>>> I'm actually looking to achieve the opposite, I want to know if it's
>>> possible to get several assemblies to log to the SAME log file. =A0Have=
 you
>>> managed to achieve this? =A0If so, do you have any example code/configs
>>> etc.?
>>>
>>> Many Thanks
>>>
>>>
>>> cristianmad wrote:
>>>>
>>>> Hi,
>>>>
>>>> I am new to log4net and just starting reading some documentation about
>>>> it.
>>>> We need to see if it would be a suitable logging solution for our
>>>> applications.
>>>> Our product (like most of them) uses a number of assemblies. I was
>>>> wondering if it would be possible for each assembly to log in its own
>>>> log
>>>> file (or any other destination) even if they are loaded in the same
>>>> application domain.
>>>> For example consider we have the following assemblies: A.dll and B.dll=
.
>>>> Is
>>>> it possible for the two assemblies to log in their own log files even =
if
>>>> they are loaded in the same application domain?
>>>> If yes, could you please give me a very simple example?
>>>>
>>>>
>>>> Thank you,
>>>> Cristian
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Log-in-more-than-1-log-destination-for-different-=
assemblies.-tp24807634p25253548.html
>>> Sent from the Log4net - Users mailing list archive at Nabble.com.
>>>
>>>
>>
>>
> :-):-):-)
> --
> View this message in context: http://www.nabble.com/Log-in-more-than-1-lo=
g-destination-for-different-assemblies.-tp24807634p25258147.html
> Sent from the Log4net - Users mailing list archive at Nabble.com.
>
>