logging-log4net-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominik Psenner <dpsen...@gmail.com>
Subject Re: unintended usage of the same configuration file
Date Sun, 11 Oct 2015 06:34:57 GMT
The concept behind how web applications work makes it hard to use file
appenders. A web application should not access a filesystem directly and
punching holes into permissions may not be advisable. If i had to work out
a web app i would log to the database that the web application will require
anyway.

jmtc
On 11 Oct 2015 4:26 a.m., "tasos" <tasoss@gmail.com> wrote:

> Hello.
> I'm working on a .net application and i have used this guidance
> http://haacked.com/archive/2005/03/07/ConfiguringLog4NetForWebApplications.aspx/
> There is a project on which i have added in the assemblyinfo.cs
> [assembly: log4net.Config.XmlConfigurator(ConfigFile = "foo1.config",
> Watch = true)]
> and in another one(different assembly)
> [assembly: log4net.Config.XmlConfigurator(ConfigFile = "foo2.config",
> Watch = true)]
> My configurations are like this http://pastebin.com/UpSpwMHH
> except the different output filenames
> (<param name="File" value="foofilename.log"/> )
> The problem is that the assembly that uses foo1.config writes on the output
> file of the file that is configured in foo2.config.
> In each class i use log4net i declare as the guidance site(mentioned
> above) says:
>
> private static readonly ILog Log = LogManager.GetLogger(MethodBase.GetCurrentMethod().DeclaringType);
>
> Thank you in advance for your help!
>
>
>

Mime
View raw message