<?xml version="1.0" encoding="utf-8" ?>
<configuration>

  <configSections>

    <!--
    In a config file where there will (potentially) be more information stored beyond just the log4net configuration information, you will need to specify a
    section to identify where the log4net configuration is housed. Here is a sample section that specifies that the configuration information will be stored
    under the XML tag "log4net"
    -->
    <section name="log4net" type="log4net.Config.Log4NetConfigurationSectionHandler, log4net"/>
  </configSections>

  <log4net>
    <!--
    You need to have one root section to house your top-level logger references. These are the loggers that inherit information from your base logger (root).
    The only other thing that the root section houses is the minimum level to log. Since everything inherits from the root, no appenders will log information below
    that specified here. This is an easy way to quickly control the logging level in your application. Here is an example with a default level of
    INFO (which means DEBUG messages will be ignored) and a reference to two appenders that should be enabled under root:
    -->
    <root>
      <level value="ALL" />
      <appender-ref ref="RollingFileAppender" />
    </root>

    <!--
    Sometimes you will want to know more about a particular part of your application. log4net anticipated this by allowing you to specify additional logger
    references beyond just the root logger.
    Note that the logger name is the full name of the class including the namespace. If you wanted to monitor an entire namespace, it would be as simple as listing
    just the namespace you wanted to monitor. I would recommend against trying to re-use appenders in multiple loggers. It can be done, but you can get some
    unpredictable results.
    Set logger name to * to target entire application
    -->
    <logger name="*">
      <!--<level value="DEBUG"/>-->
      <level value="ALL"/>
      <appender-ref ref="RollingFileAppender"/>
    </logger>

    <!--
    An appender is the name for what logs the information. It specifies where the information will be logged, how it will be logged, and under what circumstances
    the information will be logged. While each appender has different parameters based upon where the data will be going, there are some common elements.
    The first is the name and type of the appender. Each appender must be named (anything you want) and have a type assigned to it (specific to the type of
    appender desired)
    -->
    <appender name="RollingFileAppender" type="log4net.Appender.RollingFileAppender">
      <!--
      Inside of each appender must be a layout section. This may be a bit different depending on the type of appender being used, but the basics are the same.
      You need a type that specifies how the data will be written. There are multiple options, but the one that I suggest you use is the pattern layout type.
      This will allow you to specify how you want your data written to the data repository. If you specify the pattern layout type, you will need a sub-tag that
      specifies a conversion pattern. This is the pattern by which your data should be written to the data repository.
      -->
      <layout type="log4net.Layout.PatternLayout">
        <conversionPattern value="%date [%thread] %-5level %logger [%ndc] - %message%newline"/>
      </layout>

      <!-- Rolling File Appender specific settings. E.g. The name of the text file has to be specified -->
      <file value="c:\ApplicationLog\" />
      <appendToFile value="true" />
      <rollingStyle value="Date"/>
      <datePattern value="yyyy-MM-dd'.log'" />
      <maxSizeRollBackups value="90" />
      <staticLogFileName value="false" />

    </appender>

  </log4net>

  <system.diagnostics>
    <trace autoflush="true">
      <!-- Output the log4net internal debug messages by adding a trace listener -->
      <listeners>
        <add name="textWriterTraceListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="c:\ApplicationLog\log4net.log" />
      </listeners>
    </trace>
  </system.diagnostics>

</configuration>

配置文件设置完成后,需要引入下面三行代码

1. 在被跟踪的类外面加上:

[assembly: log4net.Config.XmlConfigurator(Watch = true)]

2. 在被跟踪的类中加上以下代码,创建私有的ILog实例

private static readonly log4net.ILog log = log4net.LogManager.GetLogger(System.Reflection.MethodBase.GetCurrentMethod().DeclaringType);

3. 在需要写log的地方,添加追加log的具体实现代码

log.Info("Initlaized");

log.Error("Error occured while initializing", ex);

附带详细注释的log4net的app.config文件配置例子的更多相关文章

  1. c#Winform程序调用app.config文件配置数据库连接字符串 SQL Server文章目录 浅谈SQL Server中统计对于查询的影响 有关索引的DMV SQL Server中的执行引擎入门 【译】表变量和临时表的比较 对于表列数据类型选择的一点思考 SQL Server复制入门(一)----复制简介 操作系统中的进程与线程

    c#Winform程序调用app.config文件配置数据库连接字符串 你新建winform项目的时候,会有一个app.config的配置文件,写在里面的<connectionStrings n ...

  2. Winform 数据库连接app.config文件配置 数据库连接字符串

    1.添加配置文件 新建一个winform应用程序,类似webfrom下有个web.config,winform下也有个App.config;不过 App.config不是自动生成的需要手动添加,鼠标右 ...

  3. C# app.config文件配置和修改

    很多时候我们需要对系统的.config文件进度读写操作,例如:系统初始化的参数的更改.系统参数的改变都需要更新到配置文件. 首先我们有必要了解一下app.config.exe.config和vshos ...

  4. Winform数据库连接app.config文件配置

    1.添加配置文件 新建一个winform应用程序,类似webfrom下有个web.config,winform下也有个App.config;不过 App.config不是自动生成的需要手动添加,鼠标右 ...

  5. c#Winform程序调用app.config文件配置数据库连接字符串

    你新建winform项目的时候,会有一个app.config的配置文件,写在里面的<connectionStrings name="  " connectionString= ...

  6. C#中App.config文件配置获取

    最新的framework使用如下方法: using System.Configuration; ConfigurationManager.AppSettings["key"]; A ...

  7. C# App.config文件配置数据的读写

    添加程序集引用  System.configuration.dll 和命名空间 using System.Configuration; 读: ConfigurationManager.AppSetti ...

  8. Visual Studio 2013 Unit Test Project App.config文件设置方法

    开放中经常会要做单元测试,新的项目又没有单元测试项目,怎么才能搭建一个单元测试项目呢? 下面跟我四步走,如有错误之处,还请指正! 1.添加项目 2.添加配置文件 新建app.config文件,注意不是 ...

  9. C#项目实例中读取并修改App.config文件

    C#项目是指一系列独特的.复杂的并相互关联的活动,这些活动有着一个明确的目标或目的,必须在特定的时间.预算.资源限定内,依据规范完成.项目参数包括项目范围.质量.成本.时间.资源. 1. 向C#项目实 ...

随机推荐

  1. Nightwatch.js – 轻松实现浏览器的自动测试

    Nightwatch.js 是一个易于使用的,基于 Node.js 平台的浏览器自动化测试解决方案.它使用强大的 Selenium WebDriver API 来在 DOM 元素上执行命令和断言. 语 ...

  2. CMD魔法堂:获取进程路径和PID值的方法集

    一.前言    在开发发布更更新工具——更新Weblogic应用模块时,了解到更新Weblogic应用需要先关闭Weblogic应用窗口然后是清缓存.更新应用文件,最后再重启Weblogic应用窗口. ...

  3. 转载:全球首个微信小程序(应用号)开发教程!通宵吐血赶稿,每日更新!

    微信应用号(小程序,「应用号」的新称呼)终于来了! 目前还处于内测阶段,微信只邀请了部分企业参与封测.想必大家都关心应用号的最终形态到底是什么样子?怎样将一个「服务号」改造成为「小程序」? 我们暂时以 ...

  4. Spring基础—— SpEL

    一.SpEL:Spring 表达式语言,在使用的时候类似于 EL 表达式,但是需要注意的是,SpEL 使用在 Spring Config 文件中. 二.格式:使用 #{} 作为界定符,所有在大括号中的 ...

  5. 1215 spring 3 项目更新

    列志华 (组长) http://www.cnblogs.com/liezhihua/ 团队guihub https://github.com/LWHTF/OrderingFood 黄柏堂 http:/ ...

  6. ASP.NEt MVC5--创建下拉列表

    Adding Search by Genre If you added the HttpPost version of the Index  method, delete it now. Next, ...

  7. Orleans之Hello World

    接触Orleans 有一段时间了,之前也翻译了一系列官网文档,今天我们就来一个实际的例子,来看看到底如何用这个东西来开发项目,当然经典的也是醉人的,我们就从HelloWorld开始吧. 通过前面的知识 ...

  8. P6 EPPM 16 R1 文档和帮助系统

    P6 EPPM 16 R1 文档和帮助系统 https://docs.oracle.com/cd/E74894_01/ http://docs.oracle.com/cd/E68202_01/clie ...

  9. C#设计模式——模板方法(Template Method)

    一.概述在软件开发中,对某一项操作往往有固定的算法结构,而具体的子步骤会因为不同的需要而有所不同.如何可以在稳定算法结构的同时来灵活应对子步骤变化的需求呢?二.模板方法模板方法是一种常见的设计模式,它 ...

  10. .Net配置文件——反射+配置文件存储类型实例

    配置文件+反射确实去除了选择语句的繁琐,带来了优美的赶脚! 首先改进了一下类(接上文): ? 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 ...