Databases
StackOverflow2013
Postsdbo
POImplementing single log4net config file across multiple projects
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POImplementing single log4net config file across multiple projects
    primarykey
    data
    text
    <p>I'm trying to use a solution that I've put together from a few other answers on here. Basically I'm trying to use one log4net config file for a solution that has multiple projects. </p> <p>Here is my config file:</p> <pre class="lang-xml prettyprint-override"><code>&lt;?xml version="1.0" ?&gt; &lt;log4net&gt; &lt;appender name="FileMonitorAppender" type="log4net.Appender.FileAppender"&gt; &lt;file type="log4net.Util.PatternString" value="C:\Documents and Settings\user1\My Documents\My Box Files\FOBS\logs\Box File Monitor %date{MM.dd.yyyy'_'hh.mm.ss''}.txt" /&gt; &lt;appendToFile value="true"/&gt; &lt;layout type="log4net.Layout.PatternLayout"&gt; &lt;header value="[START: Box File Monitor Run %date]%newline" type="log4net.Util.PatternString" /&gt; &lt;conversionPattern value="%date{HH:mm:ss} - %-5level- %message%newline" /&gt; &lt;footer value="[END: Box File Monitor Run]" /&gt; &lt;/layout&gt; &lt;/appender&gt; &lt;root&gt; &lt;level value="ALL"/&gt; &lt;appender-ref ref="FileMonitorAppender" /&gt; &lt;/root&gt; &lt;/log4net&gt; </code></pre> <p>and here is where I'm calling the logger in code:</p> <pre class="lang-cs prettyprint-override"><code>private static readonly ILog _log = LogManager.GetLogger("Duke.Mobile.FileMonitorAutomation.FileMonitor"); </code></pre> <p>and I also have this in the calling assembly which is supposed to configure the logger:</p> <pre class="lang-cs prettyprint-override"><code>[assembly: log4net.Config.XmlConfigurator(ConfigFile = "Log4Net.config", Watch = true)] </code></pre> <p>I have the log4net.config file in a solution folder and then have it added to the calling assembly as a linked file. When the app runs, it never hits the configuration. I've seen a couple of similar problems but it's never set up exactly this way, hoping someone can help.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPhilipp M
    1. USTrevorGoodchild
    plurals
    1. PL
      singulars
      1. LTLinked
    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. POImplementing single log4net config file across multiple projects
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POImplementing single log4net config file across multiple projects
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. COMay be this link will help you..http://stackoverflow.com/questions/17874999/log4net-for-windows-service/17875059#17875059
      singulars
      1. POImplementing single log4net config file across multiple projects
      1. USAbhishek Jain
    2. COI realized that this is a little more involved than I thought. I have a project that is implementing log4Net in the solution, as described above, and then a setup a deployment project where it appears it is actually looking for the file to do the configuration. Since I'm using a linked file, I guess I need to figure out how to reference it from the S&D project. The main objective here is to have a single configuration file that can be read from all of the separate projects.
      singulars
      1. POImplementing single log4net config file across multiple projects
      1. USTrevorGoodchild
    3. COFigured out my problem. When using a linked config file for log4net, within a Windows service project, the config file's build action needs to be set to 'Content' in the file's properties. From there, in the deployment project, the file needs to be included in the project output.
      singulars
      1. POImplementing single log4net config file across multiple projects
      1. USTrevorGoodchild
 

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