Databases
StackOverflow2013
Postsdbo
POCommon log4net logging for different instances of a dll
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCommon log4net logging for different instances of a dll
    primarykey
    data
    text
    <p>I'm having trouble configuring log4net to work the way I want. I have a class library Library.dll that is used both by my application Mine.exe and a third party aplication Other.exe. I have another class library Util.dll that is used by both Mine.exe and Library.dll.</p> <p>Mine.exe and Other.exe are run in parallel and I want the two instances of Library.dll to use the same logfile. It should also be separate from the logfile of Mine.exe. Util.dll should log to Library.dll logfile when called from Library.dll, and the Mine.exe logfile when called from Mine.exe.</p> <p><strong>Edit: I guess that was a bit hard to follow, this is how I want i to work:</strong></p> <p>Mine.exe logs to Mine.log<br> Other.exe doesn't log anything (third party application)<br> Mine.exe -> Library.dll logs to C:\Library.log<br> Other.exe -> Library.dll logs to C:\Library.log<br> Mine.exe -> Util.dll logs to Mine.log<br> Mine.exe -> Library.dll -> Util.dll logs to C:\Library.log<br> Other.exe -> Library.dll -> Util.dll logs to C:\Library.log Other.exe doesn't call Util.dll directly.</p> <p>First I tried loading a custom log4net configuration in Library.dll, using:</p> <pre><code>log4net.Config.XmlConfigurator.Configure(new FileInfo("Library.log4net.config")); </code></pre> <p>But that resulted in Mine.exe also logging to the Library.dll logfile.</p> <p>I then tried adding the following assembly attribute in Library.dll:</p> <pre><code>[assembly: log4net.Config.Repository("Library")] </code></pre> <p>That kept the logs separate, but then Util.dll logged to the Mine.exe logfile even when called from Library.dll. I guess I could use Repository("Util") in Util.dll, AliasReposity("Util", "Library") in Library.dll and AliasReposity("Util", "Mine") in Mine.exe but I actually have many class libraries in the project and would rather not go down that route.</p> <p>Any ideas on how to get this working?</p> <p>/Andreas</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAnlo
    1. USAnlo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCommon log4net logging for different instances of a dll
      1. This table or related slice is empty.
      1. VTUpMod
    1. COLet me make sure I have this straight: You want Main and Other's Library to log to log file "A", but Mine and Other themselves to log to files "B" and "C", and Util to whatever program's log file called it?
      singulars
      1. POCommon log4net logging for different instances of a dll
      1. USJames Michael Hare
    2. COYou should review your question. There seems to be some mixups with (at least) file extensions (Library.exe vs. Library.dll). Also, you probably should think about logging from an application (i.e. exe) perspective. That is, log everything from a single application into a single logfile, regardless of the DLLs that it is using. Mine.exe + all DLLs log to, say, "Mine.log". Other.exe + all DLLs log to "Other.log". Looks more intuitive to me, but of course that is just my 2 ct. :-)
      singulars
      1. POCommon log4net logging for different instances of a dll
      1. USChristian.K
    3. COYes I got the extensions mixed up, fixed now. The reason I want a common log from Library.exe is that it is almost like a separate application and I want the logging intertwined in one file. In the old COM days, I would probably have made it an out of process server instead of a dll.
      singulars
      1. POCommon log4net logging for different instances of a dll
      1. USAnlo
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload