Yes, I put the xxxx.xml file in the application root with the aspx/asmx files. Then the log file is appeared.
Thanks. 2007/8/13, Scott Glass <[EMAIL PROTECTED]>: > Hi Ron, > We use it pretty extensively in our portal. I've found it very useful to > use the XmlConfigurator attribute in the assembly.cs file. > > [log4net.Config.XmlConfigurator(logFile="xxxx.xml", watch=true)] > > Be sure "xxxx.xml" (doesn't matter what you call it) is in the > applications root with the aspx/asmx files. > > You can also configure it in the constructor, using a Uri. Just be sure you > don't call the ConfigureAndWatch method, that gets REAL ugly real fast with > open file handles. > > I brought our portal to its knees when we first started using log4net by > doing that. > > Scott > > > -----Original Message----- > From: Ron Grabowski [mailto:[EMAIL PROTECTED] > Sent: Monday, August 13, 2007 6:38 AM > To: Log4NET User > Subject: Re: How to use log4net in multi-dll Asp.net project? > > How are you configuring log4net in Global.Application_Start? > > ----- Original Message ---- > From: li nan <[EMAIL PROTECTED]> > To: [email protected] > Sent: Sunday, August 12, 2007 9:55:20 PM > Subject: How to use log4net in multi-dll Asp.net project? > > Now I'm creating an Asp.net project. I create a project called COMMON, > I add the log4net.dll to this project and create an interface, so > other project can reference this COMMON.dll and use log4net directly. > But in Asp.net project, when I use this interface, no log files are > generated. > > How to solve this problem? > > Thanks. > > > >
