It is local to the service and is placed in c:\program files\myservice\log4net.dll
Yes I enabled the internal debugging and added the section to write to file at c:\temp\log4nettest.txt and nothing is created From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, October 03, 2008 10:38 AM To: [email protected] Subject: RE: Log4net in a windows service Had you tried enabling lob4net debugging? Is log4net local to your service dll, or do you have it installed itno the GAC? ________________________________ From: Jeegnesh Sheth [mailto:[EMAIL PROTECTED] Sent: Friday, October 03, 2008 10:30 AM To: Log4NET User Subject: RE: Log4net in a windows service Chris, My config file has the same name myservice.dll.config and I was hoping that the same attributes you have would work. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, October 03, 2008 10:27 AM To: [email protected] Subject: RE: Log4net in a windows service I run a service with log4net just fine using: <Assembly: log4net.Config.XmlConfigurator(Watch:=True)> The app.config nithe service project get's turned into myservice.dll.config that sites beside of myservice.dll. For me, it just works. -=Chris ________________________________ From: Jeegnesh Sheth [mailto:[EMAIL PROTECTED] Sent: Friday, October 03, 2008 10:21 AM To: Log4NET User Subject: RE: Log4net in a windows service Radovan, Can you explain: I prefer configure log4net using app.config file or by special xml file, whose location can be got using service's EXE location (Assembly.GetExecutingAssembly().Location) In my test app, which had an APP.config, when I called my logging DLL, the right appender would get called I assumed by the attribute [Assembly: log4net.Config.XmlConfigurator(ConfigFile:="mywindowsservice.dll.config" , Watch:=True)] If I use a special file, and I get the the Assembly executing path, how would I pass this information down to log4net dll, so that the right appender is called. From: Radovan Raszka [mailto:[EMAIL PROTECTED] Sent: Friday, October 03, 2008 10:19 AM To: Log4NET User Subject: RE: Log4net in a windows service Hello, problem is usually caused by wrong config file location. If you run windows service, then service's current directory is %systemroot%\system32, not directory, where service's EXE is located on the harddisk. Because your config file is referenced by relative path, it can be searched in wrong location. I prefer configure log4net using app.config file or by special xml file, whose location can be got using service's EXE location (Assembly.GetExecutingAssembly().Location) Radovan Raszka ________________________________ From: Jeegnesh Sheth [mailto:[EMAIL PROTECTED] Sent: Friday, October 03, 2008 3:58 PM To: [email protected] Subject: Log4net in a windows service Hi, I have a logging DLL which uses log4net to log to a database. I have c# application which calls this logging DLL and log to the database. Within my logging DLL I perform additional work and hence it acts as a wrapper for log4net. In my C# windows service project, in assemblyinfo.cs I added Assembly: log4net.Config.XmlConfigurator(ConfigFile:="mywindowsservice.dll.config" , Watch:=True) This config file is where I set the appeneder. If I run my unit test it seems to work but it does not work in as a windows service. I am using system admin privileges so it is not an issue of previlige. Any thoughts?
