[jira] Resolved: (LOG4NET-48) Executed processes cannot auto find their app.config file

["Ron Grabowski (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4NET-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ron Grabowski resolved LOG4NET-48.
----------------------------------

    Resolution: Won't Fix

There haven't been any updates to this ticket in a long time. Process B can't magically find the config file of Process A unless its told where to look.

> Executed processes cannot auto find their app.config file
> ---------------------------------------------------------
>
>                 Key: LOG4NET-48
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-48
>             Project: Log4net
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.9
>            Reporter: Nicolas Roy
>            Priority: Minor
>
> Process A starts process B using the System.Diagnostics.Process.Start() method.  
> Process B use [assembly: log4net.Config.XmlConfigurator(Watch=true)] to auto configure its log4net environment.
> Process B instance of Log4net didn't succeed to initialyze itself properly.  Looks like it didn't find process B's config file.
> Work around. Process B initialyze log4net manualy:
> > 
> >             string codeBase =
> > System.Reflection.Assembly.GetEntryAssembly().CodeBase;
> > 		Uri uri = new Uri(codeBase + ".config");
> > 		log4net.Config.XmlConfigurator.Configure(new
> > FileInfo(uri.LocalPath));

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.