- [JsonContainer(ItemConverterType = typeof(MyContainerConverter), ItemConverterParameters = new object[] { 123, "Four" })]
-
-
- [JsonContainer(NamingStrategyType = typeof(MyNamingStrategy), NamingStrategyParameters = new object[] { 123, "Four" })]
-
-
- [JsonProperty(ItemConverterType = typeof(MyContainerConverter), ItemConverterParameters = new object[] { 123, "Four" })]
-
-
- [JsonProperty(NamingStrategyType = typeof(MyNamingStrategy), NamingStrategyParameters = new object[] { 123, "Four" })]
-
-
- [JsonContainer(ItemConverterType = typeof(MyContainerConverter), ItemConverterParameters = new object[] { 123, "Four" })]
-
-
- [JsonContainer(NamingStrategyType = typeof(MyNamingStrategy), NamingStrategyParameters = new object[] { 123, "Four" })]
-
-
- [JsonProperty(ItemConverterType = typeof(MyContainerConverter), ItemConverterParameters = new object[] { 123, "Four" })]
-
-
- [JsonProperty(NamingStrategyType = typeof(MyNamingStrategy), NamingStrategyParameters = new object[] { 123, "Four" })]
-
-
- [JsonContainer(ItemConverterType = typeof(MyContainerConverter), ItemConverterParameters = new object[] { 123, "Four" })]
-
-
- [JsonContainer(NamingStrategyType = typeof(MyNamingStrategy), NamingStrategyParameters = new object[] { 123, "Four" })]
-
-
- [JsonProperty(ItemConverterType = typeof(MyContainerConverter), ItemConverterParameters = new object[] { 123, "Four" })]
-
-
- [JsonProperty(NamingStrategyType = typeof(MyNamingStrategy), NamingStrategyParameters = new object[] { 123, "Four" })]
-
-
- [JsonContainer(ItemConverterType = typeof(MyContainerConverter), ItemConverterParameters = new object[] { 123, "Four" })]
-
-
- [JsonContainer(NamingStrategyType = typeof(MyNamingStrategy), NamingStrategyParameters = new object[] { 123, "Four" })]
-
-
- [JsonProperty(ItemConverterType = typeof(MyContainerConverter), ItemConverterParameters = new object[] { 123, "Four" })]
-
-
- [JsonProperty(NamingStrategyType = typeof(MyNamingStrategy), NamingStrategyParameters = new object[] { 123, "Four" })]
-
-
- [JsonContainer(ItemConverterType = typeof(MyContainerConverter), ItemConverterParameters = new object[] { 123, "Four" })]
-
-
- [JsonContainer(NamingStrategyType = typeof(MyNamingStrategy), NamingStrategyParameters = new object[] { 123, "Four" })]
-
-
- [JsonProperty(ItemConverterType = typeof(MyContainerConverter), ItemConverterParameters = new object[] { 123, "Four" })]
-
-
- [JsonProperty(NamingStrategyType = typeof(MyNamingStrategy), NamingStrategyParameters = new object[] { 123, "Four" })]
-
-
- [JsonContainer(ItemConverterType = typeof(MyContainerConverter), ItemConverterParameters = new object[] { 123, "Four" })]
-
-
- [JsonContainer(NamingStrategyType = typeof(MyNamingStrategy), NamingStrategyParameters = new object[] { 123, "Four" })]
-
-
- [JsonProperty(ItemConverterType = typeof(MyContainerConverter), ItemConverterParameters = new object[] { 123, "Four" })]
-
-
- [JsonProperty(NamingStrategyType = typeof(MyNamingStrategy), NamingStrategyParameters = new object[] { 123, "Four" })]
-
-
- [JsonContainer(ItemConverterType = typeof(MyContainerConverter), ItemConverterParameters = new object[] { 123, "Four" })]
-
-
- [JsonContainer(NamingStrategyType = typeof(MyNamingStrategy), NamingStrategyParameters = new object[] { 123, "Four" })]
-
-
- [JsonProperty(ItemConverterType = typeof(MyContainerConverter), ItemConverterParameters = new object[] { 123, "Four" })]
-
-
- [JsonProperty(NamingStrategyType = typeof(MyNamingStrategy), NamingStrategyParameters = new object[] { 123, "Four" })]
-
-
- [JsonContainer(ItemConverterType = typeof(MyContainerConverter), ItemConverterParameters = new object[] { 123, "Four" })]
-
-
- [JsonContainer(NamingStrategyType = typeof(MyNamingStrategy), NamingStrategyParameters = new object[] { 123, "Four" })]
-
-
- [JsonProperty(ItemConverterType = typeof(MyContainerConverter), ItemConverterParameters = new object[] { 123, "Four" })]
-
-
- [JsonProperty(NamingStrategyType = typeof(MyNamingStrategy), NamingStrategyParameters = new object[] { 123, "Four" })]
-
- - - -#### 软件介绍 -- SunnyUI.NET 是基于.NET Framework 4.0+、.NET6、.NET7、.NET8 框架的 C# WinForm 开源控件库、工具类库、扩展类库、多页面开发框架。 -- 源码编译环境： - 1. **VS2022 17.4**，安装.NetFramework4.0目标包的方法见：https://www.cnblogs.com/yhuse/p/15536393.html -- 动态库应用环境： **VS2010**及以上均可，支持.Net Framework 4.0+、.Net 6、.Net7 - 1. 推荐通过Nuget安装：Install-Package SunnyUI，或者通过Nuget搜索SunnyUI安装。 - 2. 不支持（.Net Framework 4 **Client Profile**）。 - -#### 软件框架 - - -#### 支持开源 -- 希望SunnyUI对您有用，您的支持也是SunnyUI开源的动力，SunnyUI有您更精彩！ - -- 感谢老板打赏，来杯咖啡提提神，写代码更有劲头！~ - -1、开源控件库 - - - 基于.Net Framework4.0，原生控件开发，参考 Element主题风格，包含 按钮、编辑框、下拉框、数据表格、工控仪表、统计图表在内的常用控件超过 **70** 个，满足常规开发需求，每个控件都精雕细琢，注重细节； - - 包含 Element 风格主题 11 个，其他主题 6 个，可通过多彩主题模式自定义主题。包含主题管理组件 UIStyleManager，可自由切换主题。 - - - - - - - - - - - - - - - - - - - - - - - - - -2、工具库 - - - 收集整理开发过程中经常用到的工具类库。 - -3、扩展库 - - - 收集整理开发过程中经常用到的扩展类库。 - -4、多页面框架 - - - 参考Element，包括7种常用框架风格，只需几行简单的代码即可创建多页面程序，其支撑组件包括UIForm，UIPage，UIFrame，集合常用控件库即可快速开发WinForm应用程序。 - - -#### 项目说明 -- 个人学习交流免费，商业应用需要授权。个人承接外包项目、个人开发商业项目等，公司内部使用、开发项目等均属于商业应用范畴。联系QQ：**17612584** 咨询授权事宜。 -- 禁止使用SunnyUI控件库开发违法应用，或使用从事其他非法目的违法犯罪行为。因此产生的法律责任与SunnyUI无关。 \ No newline at end of file diff --git a/packages/SunnyUI.3.6.7/SunnyUI.3.6.7.nupkg b/packages/SunnyUI.3.6.7/SunnyUI.3.6.7.nupkg deleted file mode 100644 index b13a701..0000000 Binary files a/packages/SunnyUI.3.6.7/SunnyUI.3.6.7.nupkg and /dev/null differ diff --git a/packages/SunnyUI.3.6.7/SunnyUI.png b/packages/SunnyUI.3.6.7/SunnyUI.png deleted file mode 100644 index 8aebfac..0000000 Binary files a/packages/SunnyUI.3.6.7/SunnyUI.png and /dev/null differ diff --git a/packages/SunnyUI.3.6.7/lib/net40/SunnyUI.dll b/packages/SunnyUI.3.6.7/lib/net40/SunnyUI.dll deleted file mode 100644 index 821cac1..0000000 Binary files a/packages/SunnyUI.3.6.7/lib/net40/SunnyUI.dll and /dev/null differ diff --git a/packages/SunnyUI.3.6.7/lib/net472/SunnyUI.dll b/packages/SunnyUI.3.6.7/lib/net472/SunnyUI.dll deleted file mode 100644 index a52e6fe..0000000 Binary files a/packages/SunnyUI.3.6.7/lib/net472/SunnyUI.dll and /dev/null differ diff --git a/packages/SunnyUI.3.6.7/lib/net6.0-windows7.0/SunnyUI.dll b/packages/SunnyUI.3.6.7/lib/net6.0-windows7.0/SunnyUI.dll deleted file mode 100644 index 2ca0d4b..0000000 Binary files a/packages/SunnyUI.3.6.7/lib/net6.0-windows7.0/SunnyUI.dll and /dev/null differ diff --git a/packages/SunnyUI.3.6.7/lib/net8.0-windows7.0/SunnyUI.dll b/packages/SunnyUI.3.6.7/lib/net8.0-windows7.0/SunnyUI.dll deleted file mode 100644 index 2ab2210..0000000 Binary files a/packages/SunnyUI.3.6.7/lib/net8.0-windows7.0/SunnyUI.dll and /dev/null differ diff --git a/packages/SunnyUI.Common.3.6.7/.signature.p7s b/packages/SunnyUI.Common.3.6.7/.signature.p7s deleted file mode 100644 index 7aec2c0..0000000 Binary files a/packages/SunnyUI.Common.3.6.7/.signature.p7s and /dev/null differ diff --git a/packages/SunnyUI.Common.3.6.7/README.md b/packages/SunnyUI.Common.3.6.7/README.md deleted file mode 100644 index ff2f291..0000000 --- a/packages/SunnyUI.Common.3.6.7/README.md +++ /dev/null @@ -1,25 +0,0 @@ -# SunnyUI.Common - - - -- Blog: https://www.cnblogs.com/yhuse -- Gitee: https://gitee.com/yhuse/SunnyUI -- GitHub: https://github.com/yhuse/SunnyUI -- Nuget: https://www.nuget.org/packages/SunnyUI -- 帮助文档目录: https://www.cnblogs.com/yhuse/p/SunnyUI_Menu.html - -欢迎交流，QQ群： 56829229 (SunnyUI技术交流群)，请给源码项目点个Star吧！！！ - -#### 介绍 -- SunnyUI.Common 是基于.Net Framework4.0+、.Net Standard2.0、.Net6、.Net7 的开源工具类库、扩展类库。 -- 源码编译环境： - **VS2022 17.4**，安装.NetFramework4.0目标包的方法见：https://www.cnblogs.com/yhuse/p/15536393.html -- 动态库应用环境：**VS2010**及以上均可： - 1. **.NetFrameWork项目**，从Nuget引用SunnyUI，或者直接引用已经编译好的Dll（SunnyUI.Common.dll） - 2. **.NetCore、.Net5、.Net6、.Net7项目**，从Nuget引用SunnyUI.Common - 3. 不支持（.Net Framework 4 **Client Profile**）。 - 4. 推荐通过Nuget安装：Install-Package SunnyUI.Common，或者通过Nuget搜索SunnyUI.Common安装。 - -#### 支持开源 -- 希望SunnyUI对您有用，您的支持也是SunnyUI开源的动力，SunnyUI有你更精彩！ - diff --git a/packages/SunnyUI.Common.3.6.7/SunnyUI.Common.3.6.7.nupkg b/packages/SunnyUI.Common.3.6.7/SunnyUI.Common.3.6.7.nupkg deleted file mode 100644 index 23b6eb6..0000000 Binary files a/packages/SunnyUI.Common.3.6.7/SunnyUI.Common.3.6.7.nupkg and /dev/null differ diff --git a/packages/SunnyUI.Common.3.6.7/SunnyUI.png b/packages/SunnyUI.Common.3.6.7/SunnyUI.png deleted file mode 100644 index 8aebfac..0000000 Binary files a/packages/SunnyUI.Common.3.6.7/SunnyUI.png and /dev/null differ diff --git a/packages/SunnyUI.Common.3.6.7/lib/net40/SunnyUI.Common.dll b/packages/SunnyUI.Common.3.6.7/lib/net40/SunnyUI.Common.dll deleted file mode 100644 index c86c3a7..0000000 Binary files a/packages/SunnyUI.Common.3.6.7/lib/net40/SunnyUI.Common.dll and /dev/null differ diff --git a/packages/SunnyUI.Common.3.6.7/lib/net472/SunnyUI.Common.dll b/packages/SunnyUI.Common.3.6.7/lib/net472/SunnyUI.Common.dll deleted file mode 100644 index 8359cd3..0000000 Binary files a/packages/SunnyUI.Common.3.6.7/lib/net472/SunnyUI.Common.dll and /dev/null differ diff --git a/packages/SunnyUI.Common.3.6.7/lib/net6.0/SunnyUI.Common.dll b/packages/SunnyUI.Common.3.6.7/lib/net6.0/SunnyUI.Common.dll deleted file mode 100644 index 567d550..0000000 Binary files a/packages/SunnyUI.Common.3.6.7/lib/net6.0/SunnyUI.Common.dll and /dev/null differ diff --git a/packages/SunnyUI.Common.3.6.7/lib/net8.0/SunnyUI.Common.dll b/packages/SunnyUI.Common.3.6.7/lib/net8.0/SunnyUI.Common.dll deleted file mode 100644 index a252654..0000000 Binary files a/packages/SunnyUI.Common.3.6.7/lib/net8.0/SunnyUI.Common.dll and /dev/null differ diff --git a/packages/log4net.2.0.17/.signature.p7s b/packages/log4net.2.0.17/.signature.p7s deleted file mode 100644 index ee3a223..0000000 Binary files a/packages/log4net.2.0.17/.signature.p7s and /dev/null differ diff --git a/packages/log4net.2.0.17/lib/net20/log4net.dll b/packages/log4net.2.0.17/lib/net20/log4net.dll deleted file mode 100644 index d6e5e03..0000000 Binary files a/packages/log4net.2.0.17/lib/net20/log4net.dll and /dev/null differ diff --git a/packages/log4net.2.0.17/lib/net20/log4net.xml b/packages/log4net.2.0.17/lib/net20/log4net.xml deleted file mode 100644 index 2e8792a..0000000 --- a/packages/log4net.2.0.17/lib/net20/log4net.xml +++ /dev/null @@ -1,31518 +0,0 @@ - -
- CREATE TABLE [dbo].[Log] (
- [ID] [int] IDENTITY (1, 1) NOT NULL ,
- [Date] [datetime] NOT NULL ,
- [Thread] [varchar] (255) NOT NULL ,
- [Level] [varchar] (20) NOT NULL ,
- [Logger] [varchar] (255) NOT NULL ,
- [Message] [varchar] (4000) NOT NULL
- ) ON [PRIMARY]
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- "DSN=MS Access Database;UID=admin;PWD=;SystemDB=C:\data\System.mdw;SafeTransactions = 0;FIL=MS Access;DriverID = 25;DBQ=C:\data\train33.mdb"
- "Driver={Microsoft Access Driver (*.mdb)};DBQ=C:\Work\cvs_root\log4net-1.2\access.mdb;UID=;PWD=;"
- "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Work\cvs_root\log4net-1.2\access.mdb;User Id=;Password=;"
- System.Data.OleDb.OleDbConnection, System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- System.Data.SqlClient.SqlConnection, System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- Microsoft.Data.Odbc.OdbcConnection,Microsoft.Data.Odbc,version=1.0.3300.0,publicKeyToken=b77a5c561934e089,culture=neutral
- This is an optional package that you can download from
- http://msdn.microsoft.com/downloads
- search for ODBC .NET Data Provider.
- System.Data.OracleClient.OracleConnection, System.Data.OracleClient, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- This is an optional package that you can download from
- http://msdn.microsoft.com/downloads
- search for .NET Managed Provider for Oracle.
-
-
-
-
-
-
- -
-
Blue
- Green
- Red
- White
- Yellow
- Purple
- Cyan
-
-
-
Bright foreground is brighter
- Dim foreground is dimmer
- Underscore message is underlined
- Blink foreground is blinking (does not work on all terminals)
- Reverse foreground and background are reversed
- Hidden output is hidden
- Strikethrough message has a line through it
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
- -
-
- Calls -and checks that - it returns true .
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
- -
-
- Calls -and checks that - it returns true .
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
-
-
-
-
-
The cyclic buffer is full and this appender is - marked as not lossy (see -)
- -
-
An -is set and - it is triggered for the - specified.
-
-
-
-
-
-
- -
-
Blue
- Green
- Red
- White
- Yellow
- Purple
- Cyan
- HighIntensity
-
- <mapping>
- <level value="ERROR" />
- <eventLogEntryType value="Error" />
- </mapping>
- <mapping>
- <level value="DEBUG" />
- <eventLogEntryType value="Information" />
- </mapping>
-
- -
-
Error an error event
- Warning a warning event
- Information an informational event
-
-
-
-
-
-
-
-
-
-
-
-
-
- -
-
-
-
Send a message to a user account on the local machine -- -- -= <name of the local machine> - - -= <user name> -
- -
-
Send a message to a user account on a remote machine -- -- -= <name of the remote machine> - - -= <user name> -
- -
-
Send a message to a domain user account -- -- -= <name of a domain controller | uninitialized> - - -= <user name> -
- -
-
Send a message to all the names in a workgroup or domain -- -- -= <workgroup name | domain name>* -
- -
-
Send a message from the local machine to a remote machine -- -- -= <name of the local machine | uninitialized> - - -= <name of the remote machine> -
-
-
-
-
- -
-
-
-
Windows NT -- -- No special group membership is required to send a network message. - -- Admin, Accounts, Print, or Server Operator group membership is required to - successfully send a network message on a remote server. - -
- -
-
Windows 2000 or later -- -- If you send a message on a domain controller that is running Active Directory, - access is allowed or denied based on the access control list (ACL) for the securable - object. The default ACL permits only Domain Admins and Account Operators to send a network message. - -- On a member server or workstation, only Administrators and Server Operators can send a network message. - -
-
-
-
- Attach date pattern for current log file
- Backup number increments for newer files
- Infinite number of backups by file size
-
-
- determine curSizeRollBackups (only within the current roll point) -
- initiates a roll over if needed for crossing a date boundary since the last run. -
- The Compact Framework does not support the
- IPEndPoint remoteEndPoint = new IPEndPoint(IPAddress.Any, 0);
- UdpClient udpClient;
- byte[] buffer;
- string loggingEvent;
-
- try
- {
- udpClient = new UdpClient(8080);
-
- while(true)
- {
- buffer = udpClient.Receive(ref remoteEndPoint);
- loggingEvent = System.Text.Encoding.Unicode.GetString(buffer);
- Console.WriteLine(loggingEvent);
- }
- }
- catch(Exception e)
- {
- Console.WriteLine(e.ToString());
- }
-
-
- Dim remoteEndPoint as IPEndPoint
- Dim udpClient as UdpClient
- Dim buffer as Byte()
- Dim loggingEvent as String
-
- Try
- remoteEndPoint = new IPEndPoint(IPAddress.Any, 0)
- udpClient = new UdpClient(8080)
-
- While True
- buffer = udpClient.Receive(ByRef remoteEndPoint)
- loggingEvent = System.Text.Encoding.Unicode.GetString(buffer)
- Console.WriteLine(loggingEvent)
- Wend
- Catch e As Exception
- Console.WriteLine(e.ToString())
- End Try
-
-
-
-
-
- -
-
-
-
224.0.0.1 -- -- Sends a message to all system on the subnet. - -
- -
-
224.0.0.2 -- -- Sends a message to all routers on the subnet. - -
- -
-
224.0.0.12 -- -- The DHCP server answers messages on the IP address 224.0.0.12, but only on a subnet. - -
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- DOMConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- DOMConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
-
-
-
-
-
-
- log4net configuration XML goes here
-
-
-
-
-
-
-
-
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- XmlConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
-
-
-
-
-
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- XmlConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
- -
-
-
-
-
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
-
-
-
-
-
Less than zero -This instance is less than -.
- -
-
Zero -This instance is equal to -.
- -
-
Greater than zero -- -This instance is greater than -. -or- -is .
-
-
-
-
-
Less than zero -is less than .
- -
-
Zero -is equal to .
- -
-
Greater than zero -is greater than .
-
-
-
-
-
WindowsIdentity.GetCurrent() 10000 loops, 00:00:00.2031250 seconds -
- -
-
WindowsIdentity.GetCurrent().Name 10000 loops, 00:00:08.0468750 seconds -
-
-
-
-
-
this events properties -- This event has -that can be set. These - properties are specific to this event only. -
- -
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
-
-
-
-
DEBUG -- The -and methods log messages - at the DEBUG level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
INFO -- The -and methods log messages - at the INFO level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
WARN -- The -and methods log messages - at the WARN level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
ERROR -- The -and methods log messages - at the ERROR level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
FATAL -- The -and methods log messages - at the FATAL level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
-
- log.Debug("This is entry number: " + i );
-
-
- if (log.IsDebugEnabled())
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- GlobalContext.Properties["hostname"] = Environment.MachineName;
-
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.Info("Application Start");
- log.Debug("This is a debug message");
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is another debug message");
- }
-
-
- log.Debug("This is entry number: " + i );
-
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- private static readonly bool isDebugEnabled = log.IsDebugEnabled;
-
-
- if (isDebugEnabled)
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- StringWriter writer = new StringWriter();
- Layout.Format(writer, loggingEvent);
- string formattedEvent = writer.ToString();
-
-
- ILog log = LogManager.GetLogger(typeof(TestApp));
- log.Debug("Message 1");
- log.Warn("Message 2");
-
-
- DEBUG [main]: Message 1
- WARN [main]: Message 2
-
- -
-
-
-
a -Equivalent to appdomain -
- -
-
appdomain -- Used to output the friendly name of the AppDomain where the - logging event was generated. - -
- -
-
aspnet-cache -- -- Used to output all cache items in the case of %aspnet-cache or just one named item if used as %aspnet-cache{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-context -- -- Used to output all context items in the case of %aspnet-context or just one named item if used as %aspnet-context{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-request -- -- Used to output all request parameters in the case of %aspnet-request or just one named param if used as %aspnet-request{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-session -- -- Used to output all session items in the case of %aspnet-session or just one named item if used as %aspnet-session{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
c -Equivalent to logger -
- -
-
C -Equivalent to type -
- -
-
class -Equivalent to type -
- -
-
d -Equivalent to date -
- -
-
date -- -- Used to output the date of the logging event in the local time zone. - To output the date in universal time use the -%utcdate pattern. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %date{HH:mm:ss,fff} or - %date{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed (). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %date{ISO8601} or %date{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
exception -- -- Used to output the exception passed in with the log message. - -- If an exception object is stored in the logging event - it will be rendered into the pattern output with a - trailing newline. - If there is no exception then nothing will be output - and no trailing newline will be appended. - It is typical to put a newline before the exception - and to have the exception as the last data in the pattern. - -
- -
-
F -Equivalent to file -
- -
-
file -- -- Used to output the file name where the logging request was - issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
identity -- -- Used to output the user name for the currently active user - (Principal.Identity.Name). - -- WARNING Generating caller information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -
- -
-
l -Equivalent to location -
- -
-
L -Equivalent to line -
- -
-
location -- -- Used to output location information of the caller which generated - the logging event. - -- The location information depends on the CLI implementation but - usually consists of the fully qualified name of the calling - method followed by the callers source the file name and line - number between parentheses. - -- The location information can be very useful. However, its - generation is extremely slow. Its use should be avoided - unless execution speed is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
level -- -- Used to output the level of the logging event. - -
- -
-
line -- -- Used to output the line number from where the logging request - was issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
logger -- -- Used to output the logger of the logging event. The - logger conversion specifier can be optionally followed by - precision specifier, that is a decimal constant in - brackets. - -- If a precision specifier is given, then only the corresponding - number of right most components of the logger name will be - printed. By default the logger name is printed in full. - -- For example, for the logger name "a.b.c" the pattern - %logger{2} will output "b.c". - -
- -
-
m -Equivalent to message -
- -
-
M -Equivalent to method -
- -
-
message -- -- Used to output the application supplied message associated with - the logging event. - -
- -
-
mdc -- -- The MDC (old name for the ThreadContext.Properties) is now part of the - combined event properties. This pattern is supported for compatibility - but is equivalent to property. - -
- -
-
method -- -- Used to output the method name where the logging request was - issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
n -Equivalent to newline -
- -
-
newline -- -- Outputs the platform dependent line separator character or - characters. - -- This conversion pattern offers the same performance as using - non-portable line separator strings such as "\n", or "\r\n". - Thus, it is the preferred way of specifying a line separator. - -
- -
-
ndc -- -- Used to output the NDC (nested diagnostic context) associated - with the thread that generated the logging event. - -
- -
-
p -Equivalent to level -
- -
-
P -Equivalent to property -
- -
-
properties -Equivalent to property -
- -
-
property -- -- Used to output the an event specific property. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %property{user} would include the value - from the property that is keyed by the string 'user'. Each property value - that is to be included in the log must be specified separately. - Properties are added to events by loggers or appenders. By default - the -log4net:HostName property is set to the name of machine on - which the event was originally logged. -- If no key is specified, e.g. %property then all the keys and their - values are printed in a comma separated list. - -- The properties of an event are combined from a number of different - contexts. These are listed below in the order in which they are searched. - --
-
-
-
the event properties -- The event has -that can be set. These - properties are specific to this event only. -
- -
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
- -
-
-
-
r -Equivalent to timestamp -
- -
-
stacktrace -- -- Used to output the stack trace of the logging event - The stack trace level specifier may be enclosed - between braces. For example, %stacktrace{level}. - If no stack trace level specifier is given then 1 is assumed - -- Output uses the format: - type3.MethodCall3 > type2.MethodCall2 > type1.MethodCall1 - -- This pattern is not available for Compact Framework assemblies. - -
- -
-
stacktracedetail -- -- Used to output the stack trace of the logging event - The stack trace level specifier may be enclosed - between braces. For example, %stacktracedetail{level}. - If no stack trace level specifier is given then 1 is assumed - -- Output uses the format: - type3.MethodCall3(type param,...) > type2.MethodCall2(type param,...) > type1.MethodCall1(type param,...) - -- This pattern is not available for Compact Framework assemblies. - -
- -
-
t -Equivalent to thread -
- -
-
timestamp -- -- Used to output the number of milliseconds elapsed since the start - of the application until the creation of the logging event. - -
- -
-
thread -- -- Used to output the name of the thread that generated the - logging event. Uses the thread number if no name is available. - -
- -
-
type -- -- Used to output the fully qualified type name of the caller - issuing the logging request. This conversion specifier - can be optionally followed by precision specifier, that - is a decimal constant in brackets. - -- If a precision specifier is given, then only the corresponding - number of right most components of the class name will be - printed. By default the class name is output in fully qualified form. - -- For example, for the class name "log4net.Layout.PatternLayout", the - pattern %type{1} will output "PatternLayout". - -- WARNING Generating the caller class information is - slow. Thus, its use should be avoided unless execution speed is - not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
u -Equivalent to identity -
- -
-
username -- -- Used to output the WindowsIdentity for the currently - active user. - -- WARNING Generating caller WindowsIdentity information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -
- -
-
utcdate -- -- Used to output the date of the logging event in universal time. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %utcdate{HH:mm:ss,fff} or - %utcdate{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed ( -). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %utcdate{ISO8601} or %utcdate{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
w -Equivalent to username -
- -
-
x -Equivalent to ndc -
- -
-
X -Equivalent to mdc -
- -
-
% -- -- The sequence %% outputs a single percent sign. - -
-
-
-
-
- | Format modifier | -left justify | -minimum width | -maximum width | -comment | -
|---|---|---|---|---|
| %20logger | -false | -20 | -none | -
- |
-
| %-20logger | -true | -20 | -none | -
- |
-
| %.30logger | -NA | -none | -30 | -
- |
-
| false | -20 | -30 | -
- |
- |
| %-20.30logger | -true | -20 | -30 | -
- |
-
- The following patterns
%timestamp [%thread] %level %logger %ndc - %message%newline
- %-6timestamp [%15.15thread] %-5level %30.30logger %ndc - %message%newline
- -
-
-
-
ISO8601 -- Uses the -formatter. - Formats using the "yyyy-MM-dd HH:mm:ss,fff" pattern. -
- -
-
DATE -- Uses the -formatter. - Formats using the "dd MMM yyyy HH:mm:ss,fff" for example,"06 Nov 1994 15:49:37,459" . -
- -
-
ABSOLUTE -- Uses the -formatter. - Formats using the "HH:mm:ss,yyyy" for example,"15:49:37,459" . -
- -
-
other -- Any other pattern string uses the -formatter. - This formatter passes the pattern string to the - method. - For details on valid patterns see - DateTimeFormatInfo Class. -
-
-
-
-
-
Message -
- -
-
Source -
- -
-
StackTrace -
- -
-
TargetSite -
- -
-
HelpLink -
-
- DEBUG - Hello world
-
-
- <?xml version="1.0" ?>
-
- <!DOCTYPE log4net:events SYSTEM "log4net-events.dtd" [<!ENTITY data SYSTEM "abc">]>
-
- <log4net:events version="1.2" xmlns:log4net="http://logging.apache.org/log4net/schemas/log4net-events-1.2>
- &data;
- </log4net:events>
-
-
- LogicalThreadContext.Properties["user"] = userName;
- log.Info("This log message has a LogicalThreadContext Property called 'user'");
-
-
- using(LogicalThreadContext.Stacks["LDC"].Push("my context message"))
- {
- log.Info("This log message has a LogicalThreadContext Stack message that includes 'my context message'");
-
- } // at the end of the using block the message is automatically popped
-
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.Info("Application Start");
- log.Debug("This is a debug message");
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is another debug message");
- }
-
-
- using(NDC.Push("my context message"))
- {
- ... all log calls will have 'my context message' included ...
-
- } // at the end of the using block the message is automatically removed
-
-
- using(log4net.NDC.Push("NDC_Message"))
- {
- log.Warn("This should have an NDC message");
- }
-
-
- var someValue = "ExampleContext"
- using(log4net.NDC.PushFormat("NDC_Message {0}", someValue))
- {
- log.Warn("This should have an NDC message");
- }
-
- -
-
-
-
null - -"(null)" -
- -
-
- -- For a one dimensional array this is the - array type name, an open brace, followed by a comma - separated list of the elements (using the appropriate - renderer), followed by a close brace. - -- For example: -int[] {1, 2, 3} . -- If the array is not one dimensional the - -Array.ToString() is returned. -
- -
-
, & - -- Rendered as an open brace, followed by a comma - separated list of the elements (using the appropriate - renderer), followed by a close brace. - -- For example: -{a, b, c} . -- All collection classes that implement -its subclasses, - or generic equivalents all implement the interface. -
- -
-
- -- Rendered as the key, an equals sign ('='), and the value (using the appropriate - renderer). - -- For example: -key=value . -
- -
-
other -- -Object.ToString()
-
-
-
-
-
No entry for the potential parent of -exists - We create a ProvisionNode for this potential - parent and insert -in that provision node. -
- -
-
The entry is of type Logger for the potential parent. -- The entry is -'s nearest existing parent. We - update 's parent field with this entry. We also break from - he loop because updating our parent's parent is our parent's - responsibility. -
- -
-
The entry is of type ProvisionNode for this potential parent. -- We add -to the list of children for this - potential parent. -
-
- ThreadContext.Properties["user"] = userName;
- log.Info("This log message has a ThreadContext Property called 'user'");
-
-
- using(ThreadContext.Stacks["NDC"].Push("my context message"))
- {
- log.Info("This log message has a ThreadContext Stack message that includes 'my context message'");
-
- } // at the end of the using block the message is automatically popped
-
-
- using(log4net.LogicalThreadContext.Stacks["NDC"].Push("Stack_Message"))
- {
- log.Warn("This should have an ThreadContext Stack message");
- }
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- string s = OptionConverter.SubstituteVariables("Value of key is ${key}.");
-
-
- string s = OptionConverter.SubstituteVariables("Value of nonExistentKey is [${nonExistentKey}]");
-
-
- {key1=value1, key2=value2, key3=value3}
-
-
- {key1=value1, key2=value2, key3=value3}
-
- -
-
-
-
appdomain -- -- Used to output the friendly name of the current AppDomain. - -
- -
-
appsetting -- -- Used to output the value of a specific appSetting key in the application - configuration file. - -
- -
-
date -- -- Used to output the current date and time in the local time zone. - To output the date in universal time use the -%utcdate pattern. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %date{HH:mm:ss,fff} or - %date{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed (). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %date{ISO8601} or %date{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
env -- -- Used to output the a specific environment variable. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %env{COMPUTERNAME} would include the value - of the -COMPUTERNAME environment variable. -- The -env pattern is not supported on the .NET Compact Framework. -
- -
-
identity -- -- Used to output the user name for the currently active user - (Principal.Identity.Name). - -
- -
-
newline -- -- Outputs the platform dependent line separator character or - characters. - -- This conversion pattern name offers the same performance as using - non-portable line separator strings such as "\n", or "\r\n". - Thus, it is the preferred way of specifying a line separator. - -
- -
-
processid -- -- Used to output the system process ID for the current process. - -
- -
-
property -- -- Used to output a specific context property. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %property{user} would include the value - from the property that is keyed by the string 'user'. Each property value - that is to be included in the log must be specified separately. - Properties are stored in logging contexts. By default - the -log4net:HostName property is set to the name of machine on - which the event was originally logged. -- If no key is specified, e.g. %property then all the keys and their - values are printed in a comma separated list. - -- The properties of an event are combined from a number of different - contexts. These are listed below in the order in which they are searched. - --
-
-
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
- -
-
-
-
random -- -- Used to output a random string of characters. The string is made up of - uppercase letters and numbers. By default the string is 4 characters long. - The length of the string can be specified within braces directly following the - pattern specifier, e.g. %random{8} would output an 8 character string. - -
- -
-
username -- -- Used to output the WindowsIdentity for the currently - active user. - -
- -
-
utcdate -- -- Used to output the date of the logging event in universal time. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %utcdate{HH:mm:ss,fff} or - %utcdate{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed ( -). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %utcdate{ISO8601} or %utcdate{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
% -- -- The sequence %% outputs a single percent sign. - -
-
-
-
-
-
ISO8601 -- Uses the -formatter. - Formats using the "yyyy-MM-dd HH:mm:ss,fff" pattern. -
- -
-
DATE -- Uses the -formatter. - Formats using the "dd MMM yyyy HH:mm:ss,fff" for example,"06 Nov 1994 15:49:37,459" . -
- -
-
ABSOLUTE -- Uses the -formatter. - Formats using the "HH:mm:ss,fff" for example,"15:49:37,459" . -
- -
-
other -- Any other pattern string uses the -formatter. - This formatter passes the pattern string to the - method. - For details on valid patterns see - DateTimeFormatInfo Class. -
-
-
-
-
-
DOS -DOS or Windows line terminator -"\r\n"
- -
-
UNIX -UNIX line terminator -"\n"
-
- using(log4net.ThreadContext.Stacks["NDC"].Push("Stack_Message"))
- {
- log.Warn("This should have an ThreadContext Stack message");
- }
-
-
- CREATE TABLE [dbo].[Log] (
- [ID] [int] IDENTITY (1, 1) NOT NULL ,
- [Date] [datetime] NOT NULL ,
- [Thread] [varchar] (255) NOT NULL ,
- [Level] [varchar] (20) NOT NULL ,
- [Logger] [varchar] (255) NOT NULL ,
- [Message] [varchar] (4000) NOT NULL
- ) ON [PRIMARY]
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- "DSN=MS Access Database;UID=admin;PWD=;SystemDB=C:\data\System.mdw;SafeTransactions = 0;FIL=MS Access;DriverID = 25;DBQ=C:\data\train33.mdb"
- "Driver={Microsoft Access Driver (*.mdb)};DBQ=C:\Work\cvs_root\log4net-1.2\access.mdb;UID=;PWD=;"
- "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Work\cvs_root\log4net-1.2\access.mdb;User Id=;Password=;"
- System.Data.OleDb.OleDbConnection, System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- System.Data.SqlClient.SqlConnection, System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- Microsoft.Data.Odbc.OdbcConnection,Microsoft.Data.Odbc,version=1.0.3300.0,publicKeyToken=b77a5c561934e089,culture=neutral
- This is an optional package that you can download from
- http://msdn.microsoft.com/downloads
- search for ODBC .NET Data Provider.
- System.Data.OracleClient.OracleConnection, System.Data.OracleClient, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- This is an optional package that you can download from
- http://msdn.microsoft.com/downloads
- search for .NET Managed Provider for Oracle.
-
-
-
-
-
-
- -
-
Blue
- Green
- Red
- White
- Yellow
- Purple
- Cyan
-
-
-
Bright foreground is brighter
- Dim foreground is dimmer
- Underscore message is underlined
- Blink foreground is blinking (does not work on all terminals)
- Reverse foreground and background are reversed
- Hidden output is hidden
- Strikethrough message has a line through it
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
- -
-
- Calls -and checks that - it returns true .
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
- -
-
- Calls -and checks that - it returns true .
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
-
-
-
-
-
The cyclic buffer is full and this appender is - marked as not lossy (see -)
- -
-
An -is set and - it is triggered for the - specified.
-
-
-
-
-
-
- -
-
Blue
- Green
- Red
- White
- Yellow
- Purple
- Cyan
- HighIntensity
-
- <mapping>
- <level value="ERROR" />
- <eventLogEntryType value="Error" />
- </mapping>
- <mapping>
- <level value="DEBUG" />
- <eventLogEntryType value="Information" />
- </mapping>
-
- -
-
Error an error event
- Warning a warning event
- Information an informational event
-
-
-
-
-
-
-
-
-
-
-
-
-
- -
-
-
-
Send a message to a user account on the local machine -- -- -= <name of the local machine> - - -= <user name> -
- -
-
Send a message to a user account on a remote machine -- -- -= <name of the remote machine> - - -= <user name> -
- -
-
Send a message to a domain user account -- -- -= <name of a domain controller | uninitialized> - - -= <user name> -
- -
-
Send a message to all the names in a workgroup or domain -- -- -= <workgroup name | domain name>* -
- -
-
Send a message from the local machine to a remote machine -- -- -= <name of the local machine | uninitialized> - - -= <name of the remote machine> -
-
-
-
-
- -
-
-
-
Windows NT -- -- No special group membership is required to send a network message. - -- Admin, Accounts, Print, or Server Operator group membership is required to - successfully send a network message on a remote server. - -
- -
-
Windows 2000 or later -- -- If you send a message on a domain controller that is running Active Directory, - access is allowed or denied based on the access control list (ACL) for the securable - object. The default ACL permits only Domain Admins and Account Operators to send a network message. - -- On a member server or workstation, only Administrators and Server Operators can send a network message. - -
-
-
-
- Attach date pattern for current log file
- Backup number increments for newer files
- Infinite number of backups by file size
-
-
- determine curSizeRollBackups (only within the current roll point) -
- initiates a roll over if needed for crossing a date boundary since the last run. -
- The Compact Framework does not support the
- IPEndPoint remoteEndPoint = new IPEndPoint(IPAddress.Any, 0);
- UdpClient udpClient;
- byte[] buffer;
- string loggingEvent;
-
- try
- {
- udpClient = new UdpClient(8080);
-
- while(true)
- {
- buffer = udpClient.Receive(ref remoteEndPoint);
- loggingEvent = System.Text.Encoding.Unicode.GetString(buffer);
- Console.WriteLine(loggingEvent);
- }
- }
- catch(Exception e)
- {
- Console.WriteLine(e.ToString());
- }
-
-
- Dim remoteEndPoint as IPEndPoint
- Dim udpClient as UdpClient
- Dim buffer as Byte()
- Dim loggingEvent as String
-
- Try
- remoteEndPoint = new IPEndPoint(IPAddress.Any, 0)
- udpClient = new UdpClient(8080)
-
- While True
- buffer = udpClient.Receive(ByRef remoteEndPoint)
- loggingEvent = System.Text.Encoding.Unicode.GetString(buffer)
- Console.WriteLine(loggingEvent)
- Wend
- Catch e As Exception
- Console.WriteLine(e.ToString())
- End Try
-
-
-
-
-
- -
-
-
-
224.0.0.1 -- -- Sends a message to all system on the subnet. - -
- -
-
224.0.0.2 -- -- Sends a message to all routers on the subnet. - -
- -
-
224.0.0.12 -- -- The DHCP server answers messages on the IP address 224.0.0.12, but only on a subnet. - -
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- DOMConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- DOMConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
-
-
-
-
-
-
- log4net configuration XML goes here
-
-
-
-
-
-
-
-
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- XmlConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
-
-
-
-
-
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- XmlConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
- -
-
-
-
-
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
-
-
-
-
-
Less than zero -This instance is less than -.
- -
-
Zero -This instance is equal to -.
- -
-
Greater than zero -- -This instance is greater than -. -or- -is .
-
-
-
-
-
Less than zero -is less than .
- -
-
Zero -is equal to .
- -
-
Greater than zero -is greater than .
-
-
-
-
-
WindowsIdentity.GetCurrent() 10000 loops, 00:00:00.2031250 seconds -
- -
-
WindowsIdentity.GetCurrent().Name 10000 loops, 00:00:08.0468750 seconds -
-
-
-
-
-
this events properties -- This event has -that can be set. These - properties are specific to this event only. -
- -
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
-
-
-
-
DEBUG -- The -and methods log messages - at the DEBUG level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
INFO -- The -and methods log messages - at the INFO level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
WARN -- The -and methods log messages - at the WARN level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
ERROR -- The -and methods log messages - at the ERROR level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
FATAL -- The -and methods log messages - at the FATAL level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
-
- log.Debug("This is entry number: " + i );
-
-
- if (log.IsDebugEnabled())
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- GlobalContext.Properties["hostname"] = Environment.MachineName;
-
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.Info("Application Start");
- log.Debug("This is a debug message");
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is another debug message");
- }
-
-
- log.Debug("This is entry number: " + i );
-
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- private static readonly bool isDebugEnabled = log.IsDebugEnabled;
-
-
- if (isDebugEnabled)
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- StringWriter writer = new StringWriter();
- Layout.Format(writer, loggingEvent);
- string formattedEvent = writer.ToString();
-
-
- ILog log = LogManager.GetLogger(typeof(TestApp));
- log.Debug("Message 1");
- log.Warn("Message 2");
-
-
- DEBUG [main]: Message 1
- WARN [main]: Message 2
-
- -
-
-
-
a -Equivalent to appdomain -
- -
-
appdomain -- Used to output the friendly name of the AppDomain where the - logging event was generated. - -
- -
-
aspnet-cache -- -- Used to output all cache items in the case of %aspnet-cache or just one named item if used as %aspnet-cache{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-context -- -- Used to output all context items in the case of %aspnet-context or just one named item if used as %aspnet-context{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-request -- -- Used to output all request parameters in the case of %aspnet-request or just one named param if used as %aspnet-request{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-session -- -- Used to output all session items in the case of %aspnet-session or just one named item if used as %aspnet-session{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
c -Equivalent to logger -
- -
-
C -Equivalent to type -
- -
-
class -Equivalent to type -
- -
-
d -Equivalent to date -
- -
-
date -- -- Used to output the date of the logging event in the local time zone. - To output the date in universal time use the -%utcdate pattern. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %date{HH:mm:ss,fff} or - %date{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed (). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %date{ISO8601} or %date{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
exception -- -- Used to output the exception passed in with the log message. - -- If an exception object is stored in the logging event - it will be rendered into the pattern output with a - trailing newline. - If there is no exception then nothing will be output - and no trailing newline will be appended. - It is typical to put a newline before the exception - and to have the exception as the last data in the pattern. - -
- -
-
F -Equivalent to file -
- -
-
file -- -- Used to output the file name where the logging request was - issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
identity -- -- Used to output the user name for the currently active user - (Principal.Identity.Name). - -- WARNING Generating caller information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -
- -
-
l -Equivalent to location -
- -
-
L -Equivalent to line -
- -
-
location -- -- Used to output location information of the caller which generated - the logging event. - -- The location information depends on the CLI implementation but - usually consists of the fully qualified name of the calling - method followed by the callers source the file name and line - number between parentheses. - -- The location information can be very useful. However, its - generation is extremely slow. Its use should be avoided - unless execution speed is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
level -- -- Used to output the level of the logging event. - -
- -
-
line -- -- Used to output the line number from where the logging request - was issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
logger -- -- Used to output the logger of the logging event. The - logger conversion specifier can be optionally followed by - precision specifier, that is a decimal constant in - brackets. - -- If a precision specifier is given, then only the corresponding - number of right most components of the logger name will be - printed. By default the logger name is printed in full. - -- For example, for the logger name "a.b.c" the pattern - %logger{2} will output "b.c". - -
- -
-
m -Equivalent to message -
- -
-
M -Equivalent to method -
- -
-
message -- -- Used to output the application supplied message associated with - the logging event. - -
- -
-
mdc -- -- The MDC (old name for the ThreadContext.Properties) is now part of the - combined event properties. This pattern is supported for compatibility - but is equivalent to property. - -
- -
-
method -- -- Used to output the method name where the logging request was - issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
n -Equivalent to newline -
- -
-
newline -- -- Outputs the platform dependent line separator character or - characters. - -- This conversion pattern offers the same performance as using - non-portable line separator strings such as "\n", or "\r\n". - Thus, it is the preferred way of specifying a line separator. - -
- -
-
ndc -- -- Used to output the NDC (nested diagnostic context) associated - with the thread that generated the logging event. - -
- -
-
p -Equivalent to level -
- -
-
P -Equivalent to property -
- -
-
properties -Equivalent to property -
- -
-
property -- -- Used to output the an event specific property. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %property{user} would include the value - from the property that is keyed by the string 'user'. Each property value - that is to be included in the log must be specified separately. - Properties are added to events by loggers or appenders. By default - the -log4net:HostName property is set to the name of machine on - which the event was originally logged. -- If no key is specified, e.g. %property then all the keys and their - values are printed in a comma separated list. - -- The properties of an event are combined from a number of different - contexts. These are listed below in the order in which they are searched. - --
-
-
-
the event properties -- The event has -that can be set. These - properties are specific to this event only. -
- -
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
- -
-
-
-
r -Equivalent to timestamp -
- -
-
stacktrace -- -- Used to output the stack trace of the logging event - The stack trace level specifier may be enclosed - between braces. For example, %stacktrace{level}. - If no stack trace level specifier is given then 1 is assumed - -- Output uses the format: - type3.MethodCall3 > type2.MethodCall2 > type1.MethodCall1 - -- This pattern is not available for Compact Framework assemblies. - -
- -
-
stacktracedetail -- -- Used to output the stack trace of the logging event - The stack trace level specifier may be enclosed - between braces. For example, %stacktracedetail{level}. - If no stack trace level specifier is given then 1 is assumed - -- Output uses the format: - type3.MethodCall3(type param,...) > type2.MethodCall2(type param,...) > type1.MethodCall1(type param,...) - -- This pattern is not available for Compact Framework assemblies. - -
- -
-
t -Equivalent to thread -
- -
-
timestamp -- -- Used to output the number of milliseconds elapsed since the start - of the application until the creation of the logging event. - -
- -
-
thread -- -- Used to output the name of the thread that generated the - logging event. Uses the thread number if no name is available. - -
- -
-
type -- -- Used to output the fully qualified type name of the caller - issuing the logging request. This conversion specifier - can be optionally followed by precision specifier, that - is a decimal constant in brackets. - -- If a precision specifier is given, then only the corresponding - number of right most components of the class name will be - printed. By default the class name is output in fully qualified form. - -- For example, for the class name "log4net.Layout.PatternLayout", the - pattern %type{1} will output "PatternLayout". - -- WARNING Generating the caller class information is - slow. Thus, its use should be avoided unless execution speed is - not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
u -Equivalent to identity -
- -
-
username -- -- Used to output the WindowsIdentity for the currently - active user. - -- WARNING Generating caller WindowsIdentity information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -
- -
-
utcdate -- -- Used to output the date of the logging event in universal time. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %utcdate{HH:mm:ss,fff} or - %utcdate{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed ( -). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %utcdate{ISO8601} or %utcdate{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
w -Equivalent to username -
- -
-
x -Equivalent to ndc -
- -
-
X -Equivalent to mdc -
- -
-
% -- -- The sequence %% outputs a single percent sign. - -
-
-
-
-
- | Format modifier | -left justify | -minimum width | -maximum width | -comment | -
|---|---|---|---|---|
| %20logger | -false | -20 | -none | -
- |
-
| %-20logger | -true | -20 | -none | -
- |
-
| %.30logger | -NA | -none | -30 | -
- |
-
| false | -20 | -30 | -
- |
- |
| %-20.30logger | -true | -20 | -30 | -
- |
-
- The following patterns
%timestamp [%thread] %level %logger %ndc - %message%newline
- %-6timestamp [%15.15thread] %-5level %30.30logger %ndc - %message%newline
- -
-
-
-
ISO8601 -- Uses the -formatter. - Formats using the "yyyy-MM-dd HH:mm:ss,fff" pattern. -
- -
-
DATE -- Uses the -formatter. - Formats using the "dd MMM yyyy HH:mm:ss,fff" for example,"06 Nov 1994 15:49:37,459" . -
- -
-
ABSOLUTE -- Uses the -formatter. - Formats using the "HH:mm:ss,yyyy" for example,"15:49:37,459" . -
- -
-
other -- Any other pattern string uses the -formatter. - This formatter passes the pattern string to the - method. - For details on valid patterns see - DateTimeFormatInfo Class. -
-
-
-
-
-
Message -
- -
-
Source -
- -
-
StackTrace -
- -
-
TargetSite -
- -
-
HelpLink -
-
- DEBUG - Hello world
-
-
- <?xml version="1.0" ?>
-
- <!DOCTYPE log4net:events SYSTEM "log4net-events.dtd" [<!ENTITY data SYSTEM "abc">]>
-
- <log4net:events version="1.2" xmlns:log4net="http://logging.apache.org/log4net/schemas/log4net-events-1.2>
- &data;
- </log4net:events>
-
-
- LogicalThreadContext.Properties["user"] = userName;
- log.Info("This log message has a LogicalThreadContext Property called 'user'");
-
-
- using(LogicalThreadContext.Stacks["LDC"].Push("my context message"))
- {
- log.Info("This log message has a LogicalThreadContext Stack message that includes 'my context message'");
-
- } // at the end of the using block the message is automatically popped
-
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.Info("Application Start");
- log.Debug("This is a debug message");
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is another debug message");
- }
-
-
- using(NDC.Push("my context message"))
- {
- ... all log calls will have 'my context message' included ...
-
- } // at the end of the using block the message is automatically removed
-
-
- using(log4net.NDC.Push("NDC_Message"))
- {
- log.Warn("This should have an NDC message");
- }
-
-
- var someValue = "ExampleContext"
- using(log4net.NDC.PushFormat("NDC_Message {0}", someValue))
- {
- log.Warn("This should have an NDC message");
- }
-
- -
-
-
-
null - -"(null)" -
- -
-
- -- For a one dimensional array this is the - array type name, an open brace, followed by a comma - separated list of the elements (using the appropriate - renderer), followed by a close brace. - -- For example: -int[] {1, 2, 3} . -- If the array is not one dimensional the - -Array.ToString() is returned. -
- -
-
, & - -- Rendered as an open brace, followed by a comma - separated list of the elements (using the appropriate - renderer), followed by a close brace. - -- For example: -{a, b, c} . -- All collection classes that implement -its subclasses, - or generic equivalents all implement the interface. -
- -
-
- -- Rendered as the key, an equals sign ('='), and the value (using the appropriate - renderer). - -- For example: -key=value . -
- -
-
other -- -Object.ToString()
-
-
-
-
-
No entry for the potential parent of -exists - We create a ProvisionNode for this potential - parent and insert -in that provision node. -
- -
-
The entry is of type Logger for the potential parent. -- The entry is -'s nearest existing parent. We - update 's parent field with this entry. We also break from - he loop because updating our parent's parent is our parent's - responsibility. -
- -
-
The entry is of type ProvisionNode for this potential parent. -- We add -to the list of children for this - potential parent. -
-
- ThreadContext.Properties["user"] = userName;
- log.Info("This log message has a ThreadContext Property called 'user'");
-
-
- using(ThreadContext.Stacks["NDC"].Push("my context message"))
- {
- log.Info("This log message has a ThreadContext Stack message that includes 'my context message'");
-
- } // at the end of the using block the message is automatically popped
-
-
- using log4net.Util;
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.InfoExt("Application Start");
- log.DebugExt("This is a debug message");
-
-
- using(log4net.LogicalThreadContext.Stacks["NDC"].Push("Stack_Message"))
- {
- log.Warn("This should have an ThreadContext Stack message");
- }
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- string s = OptionConverter.SubstituteVariables("Value of key is ${key}.");
-
-
- string s = OptionConverter.SubstituteVariables("Value of nonExistentKey is [${nonExistentKey}]");
-
-
- {key1=value1, key2=value2, key3=value3}
-
-
- {key1=value1, key2=value2, key3=value3}
-
- -
-
-
-
appdomain -- -- Used to output the friendly name of the current AppDomain. - -
- -
-
appsetting -- -- Used to output the value of a specific appSetting key in the application - configuration file. - -
- -
-
date -- -- Used to output the current date and time in the local time zone. - To output the date in universal time use the -%utcdate pattern. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %date{HH:mm:ss,fff} or - %date{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed (). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %date{ISO8601} or %date{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
env -- -- Used to output the a specific environment variable. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %env{COMPUTERNAME} would include the value - of the -COMPUTERNAME environment variable. -- The -env pattern is not supported on the .NET Compact Framework. -
- -
-
identity -- -- Used to output the user name for the currently active user - (Principal.Identity.Name). - -
- -
-
newline -- -- Outputs the platform dependent line separator character or - characters. - -- This conversion pattern name offers the same performance as using - non-portable line separator strings such as "\n", or "\r\n". - Thus, it is the preferred way of specifying a line separator. - -
- -
-
processid -- -- Used to output the system process ID for the current process. - -
- -
-
property -- -- Used to output a specific context property. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %property{user} would include the value - from the property that is keyed by the string 'user'. Each property value - that is to be included in the log must be specified separately. - Properties are stored in logging contexts. By default - the -log4net:HostName property is set to the name of machine on - which the event was originally logged. -- If no key is specified, e.g. %property then all the keys and their - values are printed in a comma separated list. - -- The properties of an event are combined from a number of different - contexts. These are listed below in the order in which they are searched. - --
-
-
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
- -
-
-
-
random -- -- Used to output a random string of characters. The string is made up of - uppercase letters and numbers. By default the string is 4 characters long. - The length of the string can be specified within braces directly following the - pattern specifier, e.g. %random{8} would output an 8 character string. - -
- -
-
username -- -- Used to output the WindowsIdentity for the currently - active user. - -
- -
-
utcdate -- -- Used to output the date of the logging event in universal time. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %utcdate{HH:mm:ss,fff} or - %utcdate{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed ( -). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %utcdate{ISO8601} or %utcdate{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
% -- -- The sequence %% outputs a single percent sign. - -
-
-
-
-
-
ISO8601 -- Uses the -formatter. - Formats using the "yyyy-MM-dd HH:mm:ss,fff" pattern. -
- -
-
DATE -- Uses the -formatter. - Formats using the "dd MMM yyyy HH:mm:ss,fff" for example,"06 Nov 1994 15:49:37,459" . -
- -
-
ABSOLUTE -- Uses the -formatter. - Formats using the "HH:mm:ss,fff" for example,"15:49:37,459" . -
- -
-
other -- Any other pattern string uses the -formatter. - This formatter passes the pattern string to the - method. - For details on valid patterns see - DateTimeFormatInfo Class. -
-
-
-
-
-
DOS -DOS or Windows line terminator -"\r\n"
- -
-
UNIX -UNIX line terminator -"\n"
-
- using(log4net.ThreadContext.Stacks["NDC"].Push("Stack_Message"))
- {
- log.Warn("This should have an ThreadContext Stack message");
- }
-
-
- CREATE TABLE [dbo].[Log] (
- [ID] [int] IDENTITY (1, 1) NOT NULL ,
- [Date] [datetime] NOT NULL ,
- [Thread] [varchar] (255) NOT NULL ,
- [Level] [varchar] (20) NOT NULL ,
- [Logger] [varchar] (255) NOT NULL ,
- [Message] [varchar] (4000) NOT NULL
- ) ON [PRIMARY]
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- "DSN=MS Access Database;UID=admin;PWD=;SystemDB=C:\data\System.mdw;SafeTransactions = 0;FIL=MS Access;DriverID = 25;DBQ=C:\data\train33.mdb"
- "Driver={Microsoft Access Driver (*.mdb)};DBQ=C:\Work\cvs_root\log4net-1.2\access.mdb;UID=;PWD=;"
- "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Work\cvs_root\log4net-1.2\access.mdb;User Id=;Password=;"
- System.Data.OleDb.OleDbConnection, System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- System.Data.SqlClient.SqlConnection, System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- Microsoft.Data.Odbc.OdbcConnection,Microsoft.Data.Odbc,version=1.0.3300.0,publicKeyToken=b77a5c561934e089,culture=neutral
- This is an optional package that you can download from
- http://msdn.microsoft.com/downloads
- search for ODBC .NET Data Provider.
- System.Data.OracleClient.OracleConnection, System.Data.OracleClient, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- This is an optional package that you can download from
- http://msdn.microsoft.com/downloads
- search for .NET Managed Provider for Oracle.
-
-
-
-
-
-
- -
-
Blue
- Green
- Red
- White
- Yellow
- Purple
- Cyan
-
-
-
Bright foreground is brighter
- Dim foreground is dimmer
- Underscore message is underlined
- Blink foreground is blinking (does not work on all terminals)
- Reverse foreground and background are reversed
- Hidden output is hidden
- Strikethrough message has a line through it
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
- -
-
- Calls -and checks that - it returns true .
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
- -
-
- Calls -and checks that - it returns true .
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
-
-
-
-
-
The cyclic buffer is full and this appender is - marked as not lossy (see -)
- -
-
An -is set and - it is triggered for the - specified.
-
-
-
-
-
-
- -
-
Blue
- Green
- Red
- White
- Yellow
- Purple
- Cyan
- HighIntensity
-
- <mapping>
- <level value="ERROR" />
- <eventLogEntryType value="Error" />
- </mapping>
- <mapping>
- <level value="DEBUG" />
- <eventLogEntryType value="Information" />
- </mapping>
-
- -
-
Error an error event
- Warning a warning event
- Information an informational event
-
-
-
-
-
-
-
-
-
-
-
-
-
- -
-
-
-
Send a message to a user account on the local machine -- -- -= <name of the local machine> - - -= <user name> -
- -
-
Send a message to a user account on a remote machine -- -- -= <name of the remote machine> - - -= <user name> -
- -
-
Send a message to a domain user account -- -- -= <name of a domain controller | uninitialized> - - -= <user name> -
- -
-
Send a message to all the names in a workgroup or domain -- -- -= <workgroup name | domain name>* -
- -
-
Send a message from the local machine to a remote machine -- -- -= <name of the local machine | uninitialized> - - -= <name of the remote machine> -
-
-
-
-
- -
-
-
-
Windows NT -- -- No special group membership is required to send a network message. - -- Admin, Accounts, Print, or Server Operator group membership is required to - successfully send a network message on a remote server. - -
- -
-
Windows 2000 or later -- -- If you send a message on a domain controller that is running Active Directory, - access is allowed or denied based on the access control list (ACL) for the securable - object. The default ACL permits only Domain Admins and Account Operators to send a network message. - -- On a member server or workstation, only Administrators and Server Operators can send a network message. - -
-
-
-
- Attach date pattern for current log file
- Backup number increments for newer files
- Infinite number of backups by file size
-
-
- determine curSizeRollBackups (only within the current roll point) -
- initiates a roll over if needed for crossing a date boundary since the last run. -
- The Compact Framework does not support the
- IPEndPoint remoteEndPoint = new IPEndPoint(IPAddress.Any, 0);
- UdpClient udpClient;
- byte[] buffer;
- string loggingEvent;
-
- try
- {
- udpClient = new UdpClient(8080);
-
- while(true)
- {
- buffer = udpClient.Receive(ref remoteEndPoint);
- loggingEvent = System.Text.Encoding.Unicode.GetString(buffer);
- Console.WriteLine(loggingEvent);
- }
- }
- catch(Exception e)
- {
- Console.WriteLine(e.ToString());
- }
-
-
- Dim remoteEndPoint as IPEndPoint
- Dim udpClient as UdpClient
- Dim buffer as Byte()
- Dim loggingEvent as String
-
- Try
- remoteEndPoint = new IPEndPoint(IPAddress.Any, 0)
- udpClient = new UdpClient(8080)
-
- While True
- buffer = udpClient.Receive(ByRef remoteEndPoint)
- loggingEvent = System.Text.Encoding.Unicode.GetString(buffer)
- Console.WriteLine(loggingEvent)
- Wend
- Catch e As Exception
- Console.WriteLine(e.ToString())
- End Try
-
-
-
-
-
- -
-
-
-
224.0.0.1 -- -- Sends a message to all system on the subnet. - -
- -
-
224.0.0.2 -- -- Sends a message to all routers on the subnet. - -
- -
-
224.0.0.12 -- -- The DHCP server answers messages on the IP address 224.0.0.12, but only on a subnet. - -
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- DOMConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- DOMConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
-
-
-
-
-
-
- log4net configuration XML goes here
-
-
-
-
-
-
-
-
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- XmlConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
-
-
-
-
-
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- XmlConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
- -
-
-
-
-
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
-
-
-
-
-
Less than zero -This instance is less than -.
- -
-
Zero -This instance is equal to -.
- -
-
Greater than zero -- -This instance is greater than -. -or- -is .
-
-
-
-
-
Less than zero -is less than .
- -
-
Zero -is equal to .
- -
-
Greater than zero -is greater than .
-
-
-
-
-
WindowsIdentity.GetCurrent() 10000 loops, 00:00:00.2031250 seconds -
- -
-
WindowsIdentity.GetCurrent().Name 10000 loops, 00:00:08.0468750 seconds -
-
-
-
-
-
this events properties -- This event has -that can be set. These - properties are specific to this event only. -
- -
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
-
-
-
-
DEBUG -- The -and methods log messages - at the DEBUG level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
INFO -- The -and methods log messages - at the INFO level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
WARN -- The -and methods log messages - at the WARN level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
ERROR -- The -and methods log messages - at the ERROR level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
FATAL -- The -and methods log messages - at the FATAL level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
-
- log.Debug("This is entry number: " + i );
-
-
- if (log.IsDebugEnabled())
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- GlobalContext.Properties["hostname"] = Environment.MachineName;
-
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.Info("Application Start");
- log.Debug("This is a debug message");
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is another debug message");
- }
-
-
- log.Debug("This is entry number: " + i );
-
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- private static readonly bool isDebugEnabled = log.IsDebugEnabled;
-
-
- if (isDebugEnabled)
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- StringWriter writer = new StringWriter();
- Layout.Format(writer, loggingEvent);
- string formattedEvent = writer.ToString();
-
-
- ILog log = LogManager.GetLogger(typeof(TestApp));
- log.Debug("Message 1");
- log.Warn("Message 2");
-
-
- DEBUG [main]: Message 1
- WARN [main]: Message 2
-
- -
-
-
-
a -Equivalent to appdomain -
- -
-
appdomain -- Used to output the friendly name of the AppDomain where the - logging event was generated. - -
- -
-
aspnet-cache -- -- Used to output all cache items in the case of %aspnet-cache or just one named item if used as %aspnet-cache{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-context -- -- Used to output all context items in the case of %aspnet-context or just one named item if used as %aspnet-context{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-request -- -- Used to output all request parameters in the case of %aspnet-request or just one named param if used as %aspnet-request{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-session -- -- Used to output all session items in the case of %aspnet-session or just one named item if used as %aspnet-session{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
c -Equivalent to logger -
- -
-
C -Equivalent to type -
- -
-
class -Equivalent to type -
- -
-
d -Equivalent to date -
- -
-
date -- -- Used to output the date of the logging event in the local time zone. - To output the date in universal time use the -%utcdate pattern. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %date{HH:mm:ss,fff} or - %date{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed (). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %date{ISO8601} or %date{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
exception -- -- Used to output the exception passed in with the log message. - -- If an exception object is stored in the logging event - it will be rendered into the pattern output with a - trailing newline. - If there is no exception then nothing will be output - and no trailing newline will be appended. - It is typical to put a newline before the exception - and to have the exception as the last data in the pattern. - -
- -
-
F -Equivalent to file -
- -
-
file -- -- Used to output the file name where the logging request was - issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
identity -- -- Used to output the user name for the currently active user - (Principal.Identity.Name). - -- WARNING Generating caller information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -
- -
-
l -Equivalent to location -
- -
-
L -Equivalent to line -
- -
-
location -- -- Used to output location information of the caller which generated - the logging event. - -- The location information depends on the CLI implementation but - usually consists of the fully qualified name of the calling - method followed by the callers source the file name and line - number between parentheses. - -- The location information can be very useful. However, its - generation is extremely slow. Its use should be avoided - unless execution speed is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
level -- -- Used to output the level of the logging event. - -
- -
-
line -- -- Used to output the line number from where the logging request - was issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
logger -- -- Used to output the logger of the logging event. The - logger conversion specifier can be optionally followed by - precision specifier, that is a decimal constant in - brackets. - -- If a precision specifier is given, then only the corresponding - number of right most components of the logger name will be - printed. By default the logger name is printed in full. - -- For example, for the logger name "a.b.c" the pattern - %logger{2} will output "b.c". - -
- -
-
m -Equivalent to message -
- -
-
M -Equivalent to method -
- -
-
message -- -- Used to output the application supplied message associated with - the logging event. - -
- -
-
mdc -- -- The MDC (old name for the ThreadContext.Properties) is now part of the - combined event properties. This pattern is supported for compatibility - but is equivalent to property. - -
- -
-
method -- -- Used to output the method name where the logging request was - issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
n -Equivalent to newline -
- -
-
newline -- -- Outputs the platform dependent line separator character or - characters. - -- This conversion pattern offers the same performance as using - non-portable line separator strings such as "\n", or "\r\n". - Thus, it is the preferred way of specifying a line separator. - -
- -
-
ndc -- -- Used to output the NDC (nested diagnostic context) associated - with the thread that generated the logging event. - -
- -
-
p -Equivalent to level -
- -
-
P -Equivalent to property -
- -
-
properties -Equivalent to property -
- -
-
property -- -- Used to output the an event specific property. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %property{user} would include the value - from the property that is keyed by the string 'user'. Each property value - that is to be included in the log must be specified separately. - Properties are added to events by loggers or appenders. By default - the -log4net:HostName property is set to the name of machine on - which the event was originally logged. -- If no key is specified, e.g. %property then all the keys and their - values are printed in a comma separated list. - -- The properties of an event are combined from a number of different - contexts. These are listed below in the order in which they are searched. - --
-
-
-
the event properties -- The event has -that can be set. These - properties are specific to this event only. -
- -
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
- -
-
-
-
r -Equivalent to timestamp -
- -
-
stacktrace -- -- Used to output the stack trace of the logging event - The stack trace level specifier may be enclosed - between braces. For example, %stacktrace{level}. - If no stack trace level specifier is given then 1 is assumed - -- Output uses the format: - type3.MethodCall3 > type2.MethodCall2 > type1.MethodCall1 - -- This pattern is not available for Compact Framework assemblies. - -
- -
-
stacktracedetail -- -- Used to output the stack trace of the logging event - The stack trace level specifier may be enclosed - between braces. For example, %stacktracedetail{level}. - If no stack trace level specifier is given then 1 is assumed - -- Output uses the format: - type3.MethodCall3(type param,...) > type2.MethodCall2(type param,...) > type1.MethodCall1(type param,...) - -- This pattern is not available for Compact Framework assemblies. - -
- -
-
t -Equivalent to thread -
- -
-
timestamp -- -- Used to output the number of milliseconds elapsed since the start - of the application until the creation of the logging event. - -
- -
-
thread -- -- Used to output the name of the thread that generated the - logging event. Uses the thread number if no name is available. - -
- -
-
type -- -- Used to output the fully qualified type name of the caller - issuing the logging request. This conversion specifier - can be optionally followed by precision specifier, that - is a decimal constant in brackets. - -- If a precision specifier is given, then only the corresponding - number of right most components of the class name will be - printed. By default the class name is output in fully qualified form. - -- For example, for the class name "log4net.Layout.PatternLayout", the - pattern %type{1} will output "PatternLayout". - -- WARNING Generating the caller class information is - slow. Thus, its use should be avoided unless execution speed is - not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
u -Equivalent to identity -
- -
-
username -- -- Used to output the WindowsIdentity for the currently - active user. - -- WARNING Generating caller WindowsIdentity information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -
- -
-
utcdate -- -- Used to output the date of the logging event in universal time. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %utcdate{HH:mm:ss,fff} or - %utcdate{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed ( -). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %utcdate{ISO8601} or %utcdate{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
w -Equivalent to username -
- -
-
x -Equivalent to ndc -
- -
-
X -Equivalent to mdc -
- -
-
% -- -- The sequence %% outputs a single percent sign. - -
-
-
-
-
- | Format modifier | -left justify | -minimum width | -maximum width | -comment | -
|---|---|---|---|---|
| %20logger | -false | -20 | -none | -
- |
-
| %-20logger | -true | -20 | -none | -
- |
-
| %.30logger | -NA | -none | -30 | -
- |
-
| false | -20 | -30 | -
- |
- |
| %-20.30logger | -true | -20 | -30 | -
- |
-
- The following patterns
%timestamp [%thread] %level %logger %ndc - %message%newline
- %-6timestamp [%15.15thread] %-5level %30.30logger %ndc - %message%newline
- -
-
-
-
ISO8601 -- Uses the -formatter. - Formats using the "yyyy-MM-dd HH:mm:ss,fff" pattern. -
- -
-
DATE -- Uses the -formatter. - Formats using the "dd MMM yyyy HH:mm:ss,fff" for example,"06 Nov 1994 15:49:37,459" . -
- -
-
ABSOLUTE -- Uses the -formatter. - Formats using the "HH:mm:ss,yyyy" for example,"15:49:37,459" . -
- -
-
other -- Any other pattern string uses the -formatter. - This formatter passes the pattern string to the - method. - For details on valid patterns see - DateTimeFormatInfo Class. -
-
-
-
-
-
Message -
- -
-
Source -
- -
-
StackTrace -
- -
-
TargetSite -
- -
-
HelpLink -
-
- DEBUG - Hello world
-
-
- <?xml version="1.0" ?>
-
- <!DOCTYPE log4net:events SYSTEM "log4net-events.dtd" [<!ENTITY data SYSTEM "abc">]>
-
- <log4net:events version="1.2" xmlns:log4net="http://logging.apache.org/log4net/schemas/log4net-events-1.2>
- &data;
- </log4net:events>
-
-
- LogicalThreadContext.Properties["user"] = userName;
- log.Info("This log message has a LogicalThreadContext Property called 'user'");
-
-
- using(LogicalThreadContext.Stacks["LDC"].Push("my context message"))
- {
- log.Info("This log message has a LogicalThreadContext Stack message that includes 'my context message'");
-
- } // at the end of the using block the message is automatically popped
-
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.Info("Application Start");
- log.Debug("This is a debug message");
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is another debug message");
- }
-
-
- using(NDC.Push("my context message"))
- {
- ... all log calls will have 'my context message' included ...
-
- } // at the end of the using block the message is automatically removed
-
-
- using(log4net.NDC.Push("NDC_Message"))
- {
- log.Warn("This should have an NDC message");
- }
-
-
- var someValue = "ExampleContext"
- using(log4net.NDC.PushFormat("NDC_Message {0}", someValue))
- {
- log.Warn("This should have an NDC message");
- }
-
- -
-
-
-
null - -"(null)" -
- -
-
- -- For a one dimensional array this is the - array type name, an open brace, followed by a comma - separated list of the elements (using the appropriate - renderer), followed by a close brace. - -- For example: -int[] {1, 2, 3} . -- If the array is not one dimensional the - -Array.ToString() is returned. -
- -
-
, & - -- Rendered as an open brace, followed by a comma - separated list of the elements (using the appropriate - renderer), followed by a close brace. - -- For example: -{a, b, c} . -- All collection classes that implement -its subclasses, - or generic equivalents all implement the interface. -
- -
-
- -- Rendered as the key, an equals sign ('='), and the value (using the appropriate - renderer). - -- For example: -key=value . -
- -
-
other -- -Object.ToString()
-
-
-
-
-
No entry for the potential parent of -exists - We create a ProvisionNode for this potential - parent and insert -in that provision node. -
- -
-
The entry is of type Logger for the potential parent. -- The entry is -'s nearest existing parent. We - update 's parent field with this entry. We also break from - he loop because updating our parent's parent is our parent's - responsibility. -
- -
-
The entry is of type ProvisionNode for this potential parent. -- We add -to the list of children for this - potential parent. -
-
- ThreadContext.Properties["user"] = userName;
- log.Info("This log message has a ThreadContext Property called 'user'");
-
-
- using(ThreadContext.Stacks["NDC"].Push("my context message"))
- {
- log.Info("This log message has a ThreadContext Stack message that includes 'my context message'");
-
- } // at the end of the using block the message is automatically popped
-
-
- using log4net.Util;
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.InfoExt("Application Start");
- log.DebugExt("This is a debug message");
-
-
- using(log4net.LogicalThreadContext.Stacks["NDC"].Push("Stack_Message"))
- {
- log.Warn("This should have an ThreadContext Stack message");
- }
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- string s = OptionConverter.SubstituteVariables("Value of key is ${key}.");
-
-
- string s = OptionConverter.SubstituteVariables("Value of nonExistentKey is [${nonExistentKey}]");
-
-
- {key1=value1, key2=value2, key3=value3}
-
-
- {key1=value1, key2=value2, key3=value3}
-
- -
-
-
-
appdomain -- -- Used to output the friendly name of the current AppDomain. - -
- -
-
appsetting -- -- Used to output the value of a specific appSetting key in the application - configuration file. - -
- -
-
date -- -- Used to output the current date and time in the local time zone. - To output the date in universal time use the -%utcdate pattern. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %date{HH:mm:ss,fff} or - %date{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed (). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %date{ISO8601} or %date{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
env -- -- Used to output the a specific environment variable. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %env{COMPUTERNAME} would include the value - of the -COMPUTERNAME environment variable. -- The -env pattern is not supported on the .NET Compact Framework. -
- -
-
identity -- -- Used to output the user name for the currently active user - (Principal.Identity.Name). - -
- -
-
newline -- -- Outputs the platform dependent line separator character or - characters. - -- This conversion pattern name offers the same performance as using - non-portable line separator strings such as "\n", or "\r\n". - Thus, it is the preferred way of specifying a line separator. - -
- -
-
processid -- -- Used to output the system process ID for the current process. - -
- -
-
property -- -- Used to output a specific context property. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %property{user} would include the value - from the property that is keyed by the string 'user'. Each property value - that is to be included in the log must be specified separately. - Properties are stored in logging contexts. By default - the -log4net:HostName property is set to the name of machine on - which the event was originally logged. -- If no key is specified, e.g. %property then all the keys and their - values are printed in a comma separated list. - -- The properties of an event are combined from a number of different - contexts. These are listed below in the order in which they are searched. - --
-
-
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
- -
-
-
-
random -- -- Used to output a random string of characters. The string is made up of - uppercase letters and numbers. By default the string is 4 characters long. - The length of the string can be specified within braces directly following the - pattern specifier, e.g. %random{8} would output an 8 character string. - -
- -
-
username -- -- Used to output the WindowsIdentity for the currently - active user. - -
- -
-
utcdate -- -- Used to output the date of the logging event in universal time. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %utcdate{HH:mm:ss,fff} or - %utcdate{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed ( -). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %utcdate{ISO8601} or %utcdate{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
% -- -- The sequence %% outputs a single percent sign. - -
-
-
-
-
-
ISO8601 -- Uses the -formatter. - Formats using the "yyyy-MM-dd HH:mm:ss,fff" pattern. -
- -
-
DATE -- Uses the -formatter. - Formats using the "dd MMM yyyy HH:mm:ss,fff" for example,"06 Nov 1994 15:49:37,459" . -
- -
-
ABSOLUTE -- Uses the -formatter. - Formats using the "HH:mm:ss,fff" for example,"15:49:37,459" . -
- -
-
other -- Any other pattern string uses the -formatter. - This formatter passes the pattern string to the - method. - For details on valid patterns see - DateTimeFormatInfo Class. -
-
-
-
-
-
DOS -DOS or Windows line terminator -"\r\n"
- -
-
UNIX -UNIX line terminator -"\n"
-
- using(log4net.ThreadContext.Stacks["NDC"].Push("Stack_Message"))
- {
- log.Warn("This should have an ThreadContext Stack message");
- }
-
-
- CREATE TABLE [dbo].[Log] (
- [ID] [int] IDENTITY (1, 1) NOT NULL ,
- [Date] [datetime] NOT NULL ,
- [Thread] [varchar] (255) NOT NULL ,
- [Level] [varchar] (20) NOT NULL ,
- [Logger] [varchar] (255) NOT NULL ,
- [Message] [varchar] (4000) NOT NULL
- ) ON [PRIMARY]
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- "DSN=MS Access Database;UID=admin;PWD=;SystemDB=C:\data\System.mdw;SafeTransactions = 0;FIL=MS Access;DriverID = 25;DBQ=C:\data\train33.mdb"
- "Driver={Microsoft Access Driver (*.mdb)};DBQ=C:\Work\cvs_root\log4net-1.2\access.mdb;UID=;PWD=;"
- "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Work\cvs_root\log4net-1.2\access.mdb;User Id=;Password=;"
- System.Data.OleDb.OleDbConnection, System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- System.Data.SqlClient.SqlConnection, System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- Microsoft.Data.Odbc.OdbcConnection,Microsoft.Data.Odbc,version=1.0.3300.0,publicKeyToken=b77a5c561934e089,culture=neutral
- This is an optional package that you can download from
- http://msdn.microsoft.com/downloads
- search for ODBC .NET Data Provider.
- System.Data.OracleClient.OracleConnection, System.Data.OracleClient, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- This is an optional package that you can download from
- http://msdn.microsoft.com/downloads
- search for .NET Managed Provider for Oracle.
-
-
-
-
-
-
- -
-
Blue
- Green
- Red
- White
- Yellow
- Purple
- Cyan
-
-
-
Bright foreground is brighter
- Dim foreground is dimmer
- Underscore message is underlined
- Blink foreground is blinking (does not work on all terminals)
- Reverse foreground and background are reversed
- Hidden output is hidden
- Strikethrough message has a line through it
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
- -
-
- Calls -and checks that - it returns true .
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
- -
-
- Calls -and checks that - it returns true .
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
-
-
-
-
-
The cyclic buffer is full and this appender is - marked as not lossy (see -)
- -
-
An -is set and - it is triggered for the - specified.
-
-
-
-
-
-
- -
-
Blue
- Green
- Red
- White
- Yellow
- Purple
- Cyan
- HighIntensity
-
- <mapping>
- <level value="ERROR" />
- <eventLogEntryType value="Error" />
- </mapping>
- <mapping>
- <level value="DEBUG" />
- <eventLogEntryType value="Information" />
- </mapping>
-
- -
-
Error an error event
- Warning a warning event
- Information an informational event
-
-
-
-
-
-
-
-
-
-
-
-
-
- -
-
-
-
Send a message to a user account on the local machine -- -- -= <name of the local machine> - - -= <user name> -
- -
-
Send a message to a user account on a remote machine -- -- -= <name of the remote machine> - - -= <user name> -
- -
-
Send a message to a domain user account -- -- -= <name of a domain controller | uninitialized> - - -= <user name> -
- -
-
Send a message to all the names in a workgroup or domain -- -- -= <workgroup name | domain name>* -
- -
-
Send a message from the local machine to a remote machine -- -- -= <name of the local machine | uninitialized> - - -= <name of the remote machine> -
-
-
-
-
- -
-
-
-
Windows NT -- -- No special group membership is required to send a network message. - -- Admin, Accounts, Print, or Server Operator group membership is required to - successfully send a network message on a remote server. - -
- -
-
Windows 2000 or later -- -- If you send a message on a domain controller that is running Active Directory, - access is allowed or denied based on the access control list (ACL) for the securable - object. The default ACL permits only Domain Admins and Account Operators to send a network message. - -- On a member server or workstation, only Administrators and Server Operators can send a network message. - -
-
-
-
- Attach date pattern for current log file
- Backup number increments for newer files
- Infinite number of backups by file size
-
-
- determine curSizeRollBackups (only within the current roll point) -
- initiates a roll over if needed for crossing a date boundary since the last run. -
- The Compact Framework does not support the
- IPEndPoint remoteEndPoint = new IPEndPoint(IPAddress.Any, 0);
- UdpClient udpClient;
- byte[] buffer;
- string loggingEvent;
-
- try
- {
- udpClient = new UdpClient(8080);
-
- while(true)
- {
- buffer = udpClient.Receive(ref remoteEndPoint);
- loggingEvent = System.Text.Encoding.Unicode.GetString(buffer);
- Console.WriteLine(loggingEvent);
- }
- }
- catch(Exception e)
- {
- Console.WriteLine(e.ToString());
- }
-
-
- Dim remoteEndPoint as IPEndPoint
- Dim udpClient as UdpClient
- Dim buffer as Byte()
- Dim loggingEvent as String
-
- Try
- remoteEndPoint = new IPEndPoint(IPAddress.Any, 0)
- udpClient = new UdpClient(8080)
-
- While True
- buffer = udpClient.Receive(ByRef remoteEndPoint)
- loggingEvent = System.Text.Encoding.Unicode.GetString(buffer)
- Console.WriteLine(loggingEvent)
- Wend
- Catch e As Exception
- Console.WriteLine(e.ToString())
- End Try
-
-
-
-
-
- -
-
-
-
224.0.0.1 -- -- Sends a message to all system on the subnet. - -
- -
-
224.0.0.2 -- -- Sends a message to all routers on the subnet. - -
- -
-
224.0.0.12 -- -- The DHCP server answers messages on the IP address 224.0.0.12, but only on a subnet. - -
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- DOMConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- DOMConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
-
-
-
-
-
-
- log4net configuration XML goes here
-
-
-
-
-
-
-
-
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- XmlConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
-
-
-
-
-
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- XmlConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
- -
-
-
-
-
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
-
-
-
-
-
Less than zero -This instance is less than -.
- -
-
Zero -This instance is equal to -.
- -
-
Greater than zero -- -This instance is greater than -. -or- -is .
-
-
-
-
-
Less than zero -is less than .
- -
-
Zero -is equal to .
- -
-
Greater than zero -is greater than .
-
-
-
-
-
WindowsIdentity.GetCurrent() 10000 loops, 00:00:00.2031250 seconds -
- -
-
WindowsIdentity.GetCurrent().Name 10000 loops, 00:00:08.0468750 seconds -
-
-
-
-
-
this events properties -- This event has -that can be set. These - properties are specific to this event only. -
- -
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
-
-
-
-
DEBUG -- The -and methods log messages - at the DEBUG level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
INFO -- The -and methods log messages - at the INFO level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
WARN -- The -and methods log messages - at the WARN level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
ERROR -- The -and methods log messages - at the ERROR level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
FATAL -- The -and methods log messages - at the FATAL level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
-
- log.Debug("This is entry number: " + i );
-
-
- if (log.IsDebugEnabled())
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- GlobalContext.Properties["hostname"] = Environment.MachineName;
-
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.Info("Application Start");
- log.Debug("This is a debug message");
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is another debug message");
- }
-
-
- log.Debug("This is entry number: " + i );
-
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- private static readonly bool isDebugEnabled = log.IsDebugEnabled;
-
-
- if (isDebugEnabled)
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- StringWriter writer = new StringWriter();
- Layout.Format(writer, loggingEvent);
- string formattedEvent = writer.ToString();
-
-
- ILog log = LogManager.GetLogger(typeof(TestApp));
- log.Debug("Message 1");
- log.Warn("Message 2");
-
-
- DEBUG [main]: Message 1
- WARN [main]: Message 2
-
- -
-
-
-
a -Equivalent to appdomain -
- -
-
appdomain -- Used to output the friendly name of the AppDomain where the - logging event was generated. - -
- -
-
aspnet-cache -- -- Used to output all cache items in the case of %aspnet-cache or just one named item if used as %aspnet-cache{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-context -- -- Used to output all context items in the case of %aspnet-context or just one named item if used as %aspnet-context{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-request -- -- Used to output all request parameters in the case of %aspnet-request or just one named param if used as %aspnet-request{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-session -- -- Used to output all session items in the case of %aspnet-session or just one named item if used as %aspnet-session{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
c -Equivalent to logger -
- -
-
C -Equivalent to type -
- -
-
class -Equivalent to type -
- -
-
d -Equivalent to date -
- -
-
date -- -- Used to output the date of the logging event in the local time zone. - To output the date in universal time use the -%utcdate pattern. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %date{HH:mm:ss,fff} or - %date{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed (). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %date{ISO8601} or %date{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
exception -- -- Used to output the exception passed in with the log message. - -- If an exception object is stored in the logging event - it will be rendered into the pattern output with a - trailing newline. - If there is no exception then nothing will be output - and no trailing newline will be appended. - It is typical to put a newline before the exception - and to have the exception as the last data in the pattern. - -
- -
-
F -Equivalent to file -
- -
-
file -- -- Used to output the file name where the logging request was - issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
identity -- -- Used to output the user name for the currently active user - (Principal.Identity.Name). - -- WARNING Generating caller information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -
- -
-
l -Equivalent to location -
- -
-
L -Equivalent to line -
- -
-
location -- -- Used to output location information of the caller which generated - the logging event. - -- The location information depends on the CLI implementation but - usually consists of the fully qualified name of the calling - method followed by the callers source the file name and line - number between parentheses. - -- The location information can be very useful. However, its - generation is extremely slow. Its use should be avoided - unless execution speed is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
level -- -- Used to output the level of the logging event. - -
- -
-
line -- -- Used to output the line number from where the logging request - was issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
logger -- -- Used to output the logger of the logging event. The - logger conversion specifier can be optionally followed by - precision specifier, that is a decimal constant in - brackets. - -- If a precision specifier is given, then only the corresponding - number of right most components of the logger name will be - printed. By default the logger name is printed in full. - -- For example, for the logger name "a.b.c" the pattern - %logger{2} will output "b.c". - -
- -
-
m -Equivalent to message -
- -
-
M -Equivalent to method -
- -
-
message -- -- Used to output the application supplied message associated with - the logging event. - -
- -
-
mdc -- -- The MDC (old name for the ThreadContext.Properties) is now part of the - combined event properties. This pattern is supported for compatibility - but is equivalent to property. - -
- -
-
method -- -- Used to output the method name where the logging request was - issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
n -Equivalent to newline -
- -
-
newline -- -- Outputs the platform dependent line separator character or - characters. - -- This conversion pattern offers the same performance as using - non-portable line separator strings such as "\n", or "\r\n". - Thus, it is the preferred way of specifying a line separator. - -
- -
-
ndc -- -- Used to output the NDC (nested diagnostic context) associated - with the thread that generated the logging event. - -
- -
-
p -Equivalent to level -
- -
-
P -Equivalent to property -
- -
-
properties -Equivalent to property -
- -
-
property -- -- Used to output the an event specific property. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %property{user} would include the value - from the property that is keyed by the string 'user'. Each property value - that is to be included in the log must be specified separately. - Properties are added to events by loggers or appenders. By default - the -log4net:HostName property is set to the name of machine on - which the event was originally logged. -- If no key is specified, e.g. %property then all the keys and their - values are printed in a comma separated list. - -- The properties of an event are combined from a number of different - contexts. These are listed below in the order in which they are searched. - --
-
-
-
the event properties -- The event has -that can be set. These - properties are specific to this event only. -
- -
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
- -
-
-
-
r -Equivalent to timestamp -
- -
-
stacktrace -- -- Used to output the stack trace of the logging event - The stack trace level specifier may be enclosed - between braces. For example, %stacktrace{level}. - If no stack trace level specifier is given then 1 is assumed - -- Output uses the format: - type3.MethodCall3 > type2.MethodCall2 > type1.MethodCall1 - -- This pattern is not available for Compact Framework assemblies. - -
- -
-
stacktracedetail -- -- Used to output the stack trace of the logging event - The stack trace level specifier may be enclosed - between braces. For example, %stacktracedetail{level}. - If no stack trace level specifier is given then 1 is assumed - -- Output uses the format: - type3.MethodCall3(type param,...) > type2.MethodCall2(type param,...) > type1.MethodCall1(type param,...) - -- This pattern is not available for Compact Framework assemblies. - -
- -
-
t -Equivalent to thread -
- -
-
timestamp -- -- Used to output the number of milliseconds elapsed since the start - of the application until the creation of the logging event. - -
- -
-
thread -- -- Used to output the name of the thread that generated the - logging event. Uses the thread number if no name is available. - -
- -
-
type -- -- Used to output the fully qualified type name of the caller - issuing the logging request. This conversion specifier - can be optionally followed by precision specifier, that - is a decimal constant in brackets. - -- If a precision specifier is given, then only the corresponding - number of right most components of the class name will be - printed. By default the class name is output in fully qualified form. - -- For example, for the class name "log4net.Layout.PatternLayout", the - pattern %type{1} will output "PatternLayout". - -- WARNING Generating the caller class information is - slow. Thus, its use should be avoided unless execution speed is - not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
u -Equivalent to identity -
- -
-
username -- -- Used to output the WindowsIdentity for the currently - active user. - -- WARNING Generating caller WindowsIdentity information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -
- -
-
utcdate -- -- Used to output the date of the logging event in universal time. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %utcdate{HH:mm:ss,fff} or - %utcdate{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed ( -). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %utcdate{ISO8601} or %utcdate{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
w -Equivalent to username -
- -
-
x -Equivalent to ndc -
- -
-
X -Equivalent to mdc -
- -
-
% -- -- The sequence %% outputs a single percent sign. - -
-
-
-
-
- | Format modifier | -left justify | -minimum width | -maximum width | -comment | -
|---|---|---|---|---|
| %20logger | -false | -20 | -none | -
- |
-
| %-20logger | -true | -20 | -none | -
- |
-
| %.30logger | -NA | -none | -30 | -
- |
-
| false | -20 | -30 | -
- |
- |
| %-20.30logger | -true | -20 | -30 | -
- |
-
- The following patterns
%timestamp [%thread] %level %logger %ndc - %message%newline
- %-6timestamp [%15.15thread] %-5level %30.30logger %ndc - %message%newline
- -
-
-
-
ISO8601 -- Uses the -formatter. - Formats using the "yyyy-MM-dd HH:mm:ss,fff" pattern. -
- -
-
DATE -- Uses the -formatter. - Formats using the "dd MMM yyyy HH:mm:ss,fff" for example,"06 Nov 1994 15:49:37,459" . -
- -
-
ABSOLUTE -- Uses the -formatter. - Formats using the "HH:mm:ss,yyyy" for example,"15:49:37,459" . -
- -
-
other -- Any other pattern string uses the -formatter. - This formatter passes the pattern string to the - method. - For details on valid patterns see - DateTimeFormatInfo Class. -
-
-
-
-
-
Message -
- -
-
Source -
- -
-
StackTrace -
- -
-
TargetSite -
- -
-
HelpLink -
-
- DEBUG - Hello world
-
-
- <?xml version="1.0" ?>
-
- <!DOCTYPE log4net:events SYSTEM "log4net-events.dtd" [<!ENTITY data SYSTEM "abc">]>
-
- <log4net:events version="1.2" xmlns:log4net="http://logging.apache.org/log4net/schemas/log4net-events-1.2>
- &data;
- </log4net:events>
-
-
- LogicalThreadContext.Properties["user"] = userName;
- log.Info("This log message has a LogicalThreadContext Property called 'user'");
-
-
- using(LogicalThreadContext.Stacks["LDC"].Push("my context message"))
- {
- log.Info("This log message has a LogicalThreadContext Stack message that includes 'my context message'");
-
- } // at the end of the using block the message is automatically popped
-
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.Info("Application Start");
- log.Debug("This is a debug message");
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is another debug message");
- }
-
-
- using(NDC.Push("my context message"))
- {
- ... all log calls will have 'my context message' included ...
-
- } // at the end of the using block the message is automatically removed
-
-
- using(log4net.NDC.Push("NDC_Message"))
- {
- log.Warn("This should have an NDC message");
- }
-
-
- var someValue = "ExampleContext"
- using(log4net.NDC.PushFormat("NDC_Message {0}", someValue))
- {
- log.Warn("This should have an NDC message");
- }
-
- -
-
-
-
null - -"(null)" -
- -
-
- -- For a one dimensional array this is the - array type name, an open brace, followed by a comma - separated list of the elements (using the appropriate - renderer), followed by a close brace. - -- For example: -int[] {1, 2, 3} . -- If the array is not one dimensional the - -Array.ToString() is returned. -
- -
-
, & - -- Rendered as an open brace, followed by a comma - separated list of the elements (using the appropriate - renderer), followed by a close brace. - -- For example: -{a, b, c} . -- All collection classes that implement -its subclasses, - or generic equivalents all implement the interface. -
- -
-
- -- Rendered as the key, an equals sign ('='), and the value (using the appropriate - renderer). - -- For example: -key=value . -
- -
-
other -- -Object.ToString()
-
-
-
-
-
No entry for the potential parent of -exists - We create a ProvisionNode for this potential - parent and insert -in that provision node. -
- -
-
The entry is of type Logger for the potential parent. -- The entry is -'s nearest existing parent. We - update 's parent field with this entry. We also break from - he loop because updating our parent's parent is our parent's - responsibility. -
- -
-
The entry is of type ProvisionNode for this potential parent. -- We add -to the list of children for this - potential parent. -
-
- ThreadContext.Properties["user"] = userName;
- log.Info("This log message has a ThreadContext Property called 'user'");
-
-
- using(ThreadContext.Stacks["NDC"].Push("my context message"))
- {
- log.Info("This log message has a ThreadContext Stack message that includes 'my context message'");
-
- } // at the end of the using block the message is automatically popped
-
-
- using log4net.Util;
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.InfoExt("Application Start");
- log.DebugExt("This is a debug message");
-
-
- using(log4net.LogicalThreadContext.Stacks["NDC"].Push("Stack_Message"))
- {
- log.Warn("This should have an ThreadContext Stack message");
- }
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- string s = OptionConverter.SubstituteVariables("Value of key is ${key}.");
-
-
- string s = OptionConverter.SubstituteVariables("Value of nonExistentKey is [${nonExistentKey}]");
-
-
- {key1=value1, key2=value2, key3=value3}
-
-
- {key1=value1, key2=value2, key3=value3}
-
- -
-
-
-
appdomain -- -- Used to output the friendly name of the current AppDomain. - -
- -
-
appsetting -- -- Used to output the value of a specific appSetting key in the application - configuration file. - -
- -
-
date -- -- Used to output the current date and time in the local time zone. - To output the date in universal time use the -%utcdate pattern. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %date{HH:mm:ss,fff} or - %date{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed (). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %date{ISO8601} or %date{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
env -- -- Used to output the a specific environment variable. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %env{COMPUTERNAME} would include the value - of the -COMPUTERNAME environment variable. -- The -env pattern is not supported on the .NET Compact Framework. -
- -
-
identity -- -- Used to output the user name for the currently active user - (Principal.Identity.Name). - -
- -
-
newline -- -- Outputs the platform dependent line separator character or - characters. - -- This conversion pattern name offers the same performance as using - non-portable line separator strings such as "\n", or "\r\n". - Thus, it is the preferred way of specifying a line separator. - -
- -
-
processid -- -- Used to output the system process ID for the current process. - -
- -
-
property -- -- Used to output a specific context property. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %property{user} would include the value - from the property that is keyed by the string 'user'. Each property value - that is to be included in the log must be specified separately. - Properties are stored in logging contexts. By default - the -log4net:HostName property is set to the name of machine on - which the event was originally logged. -- If no key is specified, e.g. %property then all the keys and their - values are printed in a comma separated list. - -- The properties of an event are combined from a number of different - contexts. These are listed below in the order in which they are searched. - --
-
-
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
- -
-
-
-
random -- -- Used to output a random string of characters. The string is made up of - uppercase letters and numbers. By default the string is 4 characters long. - The length of the string can be specified within braces directly following the - pattern specifier, e.g. %random{8} would output an 8 character string. - -
- -
-
username -- -- Used to output the WindowsIdentity for the currently - active user. - -
- -
-
utcdate -- -- Used to output the date of the logging event in universal time. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %utcdate{HH:mm:ss,fff} or - %utcdate{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed ( -). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %utcdate{ISO8601} or %utcdate{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
% -- -- The sequence %% outputs a single percent sign. - -
-
-
-
-
-
ISO8601 -- Uses the -formatter. - Formats using the "yyyy-MM-dd HH:mm:ss,fff" pattern. -
- -
-
DATE -- Uses the -formatter. - Formats using the "dd MMM yyyy HH:mm:ss,fff" for example,"06 Nov 1994 15:49:37,459" . -
- -
-
ABSOLUTE -- Uses the -formatter. - Formats using the "HH:mm:ss,fff" for example,"15:49:37,459" . -
- -
-
other -- Any other pattern string uses the -formatter. - This formatter passes the pattern string to the - method. - For details on valid patterns see - DateTimeFormatInfo Class. -
-
-
-
-
-
DOS -DOS or Windows line terminator -"\r\n"
- -
-
UNIX -UNIX line terminator -"\n"
-
- using(log4net.ThreadContext.Stacks["NDC"].Push("Stack_Message"))
- {
- log.Warn("This should have an ThreadContext Stack message");
- }
-
-
- CREATE TABLE [dbo].[Log] (
- [ID] [int] IDENTITY (1, 1) NOT NULL ,
- [Date] [datetime] NOT NULL ,
- [Thread] [varchar] (255) NOT NULL ,
- [Level] [varchar] (20) NOT NULL ,
- [Logger] [varchar] (255) NOT NULL ,
- [Message] [varchar] (4000) NOT NULL
- ) ON [PRIMARY]
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- "DSN=MS Access Database;UID=admin;PWD=;SystemDB=C:\data\System.mdw;SafeTransactions = 0;FIL=MS Access;DriverID = 25;DBQ=C:\data\train33.mdb"
- "Driver={Microsoft Access Driver (*.mdb)};DBQ=C:\Work\cvs_root\log4net-1.2\access.mdb;UID=;PWD=;"
- "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Work\cvs_root\log4net-1.2\access.mdb;User Id=;Password=;"
- System.Data.OleDb.OleDbConnection, System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- System.Data.SqlClient.SqlConnection, System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- Microsoft.Data.Odbc.OdbcConnection,Microsoft.Data.Odbc,version=1.0.3300.0,publicKeyToken=b77a5c561934e089,culture=neutral
- This is an optional package that you can download from
- http://msdn.microsoft.com/downloads
- search for ODBC .NET Data Provider.
- System.Data.OracleClient.OracleConnection, System.Data.OracleClient, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- This is an optional package that you can download from
- http://msdn.microsoft.com/downloads
- search for .NET Managed Provider for Oracle.
-
-
-
-
-
-
- -
-
Blue
- Green
- Red
- White
- Yellow
- Purple
- Cyan
-
-
-
Bright foreground is brighter
- Dim foreground is dimmer
- Underscore message is underlined
- Blink foreground is blinking (does not work on all terminals)
- Reverse foreground and background are reversed
- Hidden output is hidden
- Strikethrough message has a line through it
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
- -
-
- Calls -and checks that - it returns true .
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
- -
-
- Calls -and checks that - it returns true .
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
-
-
-
-
-
The cyclic buffer is full and this appender is - marked as not lossy (see -)
- -
-
An -is set and - it is triggered for the - specified.
-
-
-
-
-
-
- -
-
Blue
- Green
- Red
- White
- Yellow
- Purple
- Cyan
- HighIntensity
-
- <mapping>
- <level value="ERROR" />
- <eventLogEntryType value="Error" />
- </mapping>
- <mapping>
- <level value="DEBUG" />
- <eventLogEntryType value="Information" />
- </mapping>
-
- -
-
Error an error event
- Warning a warning event
- Information an informational event
-
-
-
-
-
-
-
-
-
-
-
-
-
- -
-
-
-
Send a message to a user account on the local machine -- -- -= <name of the local machine> - - -= <user name> -
- -
-
Send a message to a user account on a remote machine -- -- -= <name of the remote machine> - - -= <user name> -
- -
-
Send a message to a domain user account -- -- -= <name of a domain controller | uninitialized> - - -= <user name> -
- -
-
Send a message to all the names in a workgroup or domain -- -- -= <workgroup name | domain name>* -
- -
-
Send a message from the local machine to a remote machine -- -- -= <name of the local machine | uninitialized> - - -= <name of the remote machine> -
-
-
-
-
- -
-
-
-
Windows NT -- -- No special group membership is required to send a network message. - -- Admin, Accounts, Print, or Server Operator group membership is required to - successfully send a network message on a remote server. - -
- -
-
Windows 2000 or later -- -- If you send a message on a domain controller that is running Active Directory, - access is allowed or denied based on the access control list (ACL) for the securable - object. The default ACL permits only Domain Admins and Account Operators to send a network message. - -- On a member server or workstation, only Administrators and Server Operators can send a network message. - -
-
-
-
- Attach date pattern for current log file
- Backup number increments for newer files
- Infinite number of backups by file size
-
-
- determine curSizeRollBackups (only within the current roll point) -
- initiates a roll over if needed for crossing a date boundary since the last run. -
- The Compact Framework does not support the
- IPEndPoint remoteEndPoint = new IPEndPoint(IPAddress.Any, 0);
- UdpClient udpClient;
- byte[] buffer;
- string loggingEvent;
-
- try
- {
- udpClient = new UdpClient(8080);
-
- while(true)
- {
- buffer = udpClient.Receive(ref remoteEndPoint);
- loggingEvent = System.Text.Encoding.Unicode.GetString(buffer);
- Console.WriteLine(loggingEvent);
- }
- }
- catch(Exception e)
- {
- Console.WriteLine(e.ToString());
- }
-
-
- Dim remoteEndPoint as IPEndPoint
- Dim udpClient as UdpClient
- Dim buffer as Byte()
- Dim loggingEvent as String
-
- Try
- remoteEndPoint = new IPEndPoint(IPAddress.Any, 0)
- udpClient = new UdpClient(8080)
-
- While True
- buffer = udpClient.Receive(ByRef remoteEndPoint)
- loggingEvent = System.Text.Encoding.Unicode.GetString(buffer)
- Console.WriteLine(loggingEvent)
- Wend
- Catch e As Exception
- Console.WriteLine(e.ToString())
- End Try
-
-
-
-
-
- -
-
-
-
224.0.0.1 -- -- Sends a message to all system on the subnet. - -
- -
-
224.0.0.2 -- -- Sends a message to all routers on the subnet. - -
- -
-
224.0.0.12 -- -- The DHCP server answers messages on the IP address 224.0.0.12, but only on a subnet. - -
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- DOMConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- DOMConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
-
-
-
-
-
-
- log4net configuration XML goes here
-
-
-
-
-
-
-
-
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- XmlConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
-
-
-
-
-
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- XmlConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
- -
-
-
-
-
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
-
-
-
-
-
Less than zero -This instance is less than -.
- -
-
Zero -This instance is equal to -.
- -
-
Greater than zero -- -This instance is greater than -. -or- -is .
-
-
-
-
-
Less than zero -is less than .
- -
-
Zero -is equal to .
- -
-
Greater than zero -is greater than .
-
-
-
-
-
WindowsIdentity.GetCurrent() 10000 loops, 00:00:00.2031250 seconds -
- -
-
WindowsIdentity.GetCurrent().Name 10000 loops, 00:00:08.0468750 seconds -
-
-
-
-
-
this events properties -- This event has -that can be set. These - properties are specific to this event only. -
- -
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
-
-
-
-
DEBUG -- The -and methods log messages - at the DEBUG level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
INFO -- The -and methods log messages - at the INFO level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
WARN -- The -and methods log messages - at the WARN level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
ERROR -- The -and methods log messages - at the ERROR level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
FATAL -- The -and methods log messages - at the FATAL level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
-
- log.Debug("This is entry number: " + i );
-
-
- if (log.IsDebugEnabled())
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- GlobalContext.Properties["hostname"] = Environment.MachineName;
-
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.Info("Application Start");
- log.Debug("This is a debug message");
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is another debug message");
- }
-
-
- log.Debug("This is entry number: " + i );
-
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- private static readonly bool isDebugEnabled = log.IsDebugEnabled;
-
-
- if (isDebugEnabled)
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- StringWriter writer = new StringWriter();
- Layout.Format(writer, loggingEvent);
- string formattedEvent = writer.ToString();
-
-
- ILog log = LogManager.GetLogger(typeof(TestApp));
- log.Debug("Message 1");
- log.Warn("Message 2");
-
-
- DEBUG [main]: Message 1
- WARN [main]: Message 2
-
- -
-
-
-
a -Equivalent to appdomain -
- -
-
appdomain -- Used to output the friendly name of the AppDomain where the - logging event was generated. - -
- -
-
aspnet-cache -- -- Used to output all cache items in the case of %aspnet-cache or just one named item if used as %aspnet-cache{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-context -- -- Used to output all context items in the case of %aspnet-context or just one named item if used as %aspnet-context{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-request -- -- Used to output all request parameters in the case of %aspnet-request or just one named param if used as %aspnet-request{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-session -- -- Used to output all session items in the case of %aspnet-session or just one named item if used as %aspnet-session{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
c -Equivalent to logger -
- -
-
C -Equivalent to type -
- -
-
class -Equivalent to type -
- -
-
d -Equivalent to date -
- -
-
date -- -- Used to output the date of the logging event in the local time zone. - To output the date in universal time use the -%utcdate pattern. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %date{HH:mm:ss,fff} or - %date{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed (). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %date{ISO8601} or %date{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
exception -- -- Used to output the exception passed in with the log message. - -- If an exception object is stored in the logging event - it will be rendered into the pattern output with a - trailing newline. - If there is no exception then nothing will be output - and no trailing newline will be appended. - It is typical to put a newline before the exception - and to have the exception as the last data in the pattern. - -
- -
-
F -Equivalent to file -
- -
-
file -- -- Used to output the file name where the logging request was - issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
identity -- -- Used to output the user name for the currently active user - (Principal.Identity.Name). - -- WARNING Generating caller information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -
- -
-
l -Equivalent to location -
- -
-
L -Equivalent to line -
- -
-
location -- -- Used to output location information of the caller which generated - the logging event. - -- The location information depends on the CLI implementation but - usually consists of the fully qualified name of the calling - method followed by the callers source the file name and line - number between parentheses. - -- The location information can be very useful. However, its - generation is extremely slow. Its use should be avoided - unless execution speed is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
level -- -- Used to output the level of the logging event. - -
- -
-
line -- -- Used to output the line number from where the logging request - was issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
logger -- -- Used to output the logger of the logging event. The - logger conversion specifier can be optionally followed by - precision specifier, that is a decimal constant in - brackets. - -- If a precision specifier is given, then only the corresponding - number of right most components of the logger name will be - printed. By default the logger name is printed in full. - -- For example, for the logger name "a.b.c" the pattern - %logger{2} will output "b.c". - -
- -
-
m -Equivalent to message -
- -
-
M -Equivalent to method -
- -
-
message -- -- Used to output the application supplied message associated with - the logging event. - -
- -
-
mdc -- -- The MDC (old name for the ThreadContext.Properties) is now part of the - combined event properties. This pattern is supported for compatibility - but is equivalent to property. - -
- -
-
method -- -- Used to output the method name where the logging request was - issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
n -Equivalent to newline -
- -
-
newline -- -- Outputs the platform dependent line separator character or - characters. - -- This conversion pattern offers the same performance as using - non-portable line separator strings such as "\n", or "\r\n". - Thus, it is the preferred way of specifying a line separator. - -
- -
-
ndc -- -- Used to output the NDC (nested diagnostic context) associated - with the thread that generated the logging event. - -
- -
-
p -Equivalent to level -
- -
-
P -Equivalent to property -
- -
-
properties -Equivalent to property -
- -
-
property -- -- Used to output the an event specific property. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %property{user} would include the value - from the property that is keyed by the string 'user'. Each property value - that is to be included in the log must be specified separately. - Properties are added to events by loggers or appenders. By default - the -log4net:HostName property is set to the name of machine on - which the event was originally logged. -- If no key is specified, e.g. %property then all the keys and their - values are printed in a comma separated list. - -- The properties of an event are combined from a number of different - contexts. These are listed below in the order in which they are searched. - --
-
-
-
the event properties -- The event has -that can be set. These - properties are specific to this event only. -
- -
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
- -
-
-
-
r -Equivalent to timestamp -
- -
-
stacktrace -- -- Used to output the stack trace of the logging event - The stack trace level specifier may be enclosed - between braces. For example, %stacktrace{level}. - If no stack trace level specifier is given then 1 is assumed - -- Output uses the format: - type3.MethodCall3 > type2.MethodCall2 > type1.MethodCall1 - -- This pattern is not available for Compact Framework assemblies. - -
- -
-
stacktracedetail -- -- Used to output the stack trace of the logging event - The stack trace level specifier may be enclosed - between braces. For example, %stacktracedetail{level}. - If no stack trace level specifier is given then 1 is assumed - -- Output uses the format: - type3.MethodCall3(type param,...) > type2.MethodCall2(type param,...) > type1.MethodCall1(type param,...) - -- This pattern is not available for Compact Framework assemblies. - -
- -
-
t -Equivalent to thread -
- -
-
timestamp -- -- Used to output the number of milliseconds elapsed since the start - of the application until the creation of the logging event. - -
- -
-
thread -- -- Used to output the name of the thread that generated the - logging event. Uses the thread number if no name is available. - -
- -
-
type -- -- Used to output the fully qualified type name of the caller - issuing the logging request. This conversion specifier - can be optionally followed by precision specifier, that - is a decimal constant in brackets. - -- If a precision specifier is given, then only the corresponding - number of right most components of the class name will be - printed. By default the class name is output in fully qualified form. - -- For example, for the class name "log4net.Layout.PatternLayout", the - pattern %type{1} will output "PatternLayout". - -- WARNING Generating the caller class information is - slow. Thus, its use should be avoided unless execution speed is - not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
u -Equivalent to identity -
- -
-
username -- -- Used to output the WindowsIdentity for the currently - active user. - -- WARNING Generating caller WindowsIdentity information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -
- -
-
utcdate -- -- Used to output the date of the logging event in universal time. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %utcdate{HH:mm:ss,fff} or - %utcdate{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed ( -). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %utcdate{ISO8601} or %utcdate{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
w -Equivalent to username -
- -
-
x -Equivalent to ndc -
- -
-
X -Equivalent to mdc -
- -
-
% -- -- The sequence %% outputs a single percent sign. - -
-
-
-
-
- | Format modifier | -left justify | -minimum width | -maximum width | -comment | -
|---|---|---|---|---|
| %20logger | -false | -20 | -none | -
- |
-
| %-20logger | -true | -20 | -none | -
- |
-
| %.30logger | -NA | -none | -30 | -
- |
-
| false | -20 | -30 | -
- |
- |
| %-20.30logger | -true | -20 | -30 | -
- |
-
- The following patterns
%timestamp [%thread] %level %logger %ndc - %message%newline
- %-6timestamp [%15.15thread] %-5level %30.30logger %ndc - %message%newline
- -
-
-
-
ISO8601 -- Uses the -formatter. - Formats using the "yyyy-MM-dd HH:mm:ss,fff" pattern. -
- -
-
DATE -- Uses the -formatter. - Formats using the "dd MMM yyyy HH:mm:ss,fff" for example,"06 Nov 1994 15:49:37,459" . -
- -
-
ABSOLUTE -- Uses the -formatter. - Formats using the "HH:mm:ss,yyyy" for example,"15:49:37,459" . -
- -
-
other -- Any other pattern string uses the -formatter. - This formatter passes the pattern string to the - method. - For details on valid patterns see - DateTimeFormatInfo Class. -
-
-
-
-
-
Message -
- -
-
Source -
- -
-
StackTrace -
- -
-
TargetSite -
- -
-
HelpLink -
-
- DEBUG - Hello world
-
-
- <?xml version="1.0" ?>
-
- <!DOCTYPE log4net:events SYSTEM "log4net-events.dtd" [<!ENTITY data SYSTEM "abc">]>
-
- <log4net:events version="1.2" xmlns:log4net="http://logging.apache.org/log4net/schemas/log4net-events-1.2>
- &data;
- </log4net:events>
-
-
- LogicalThreadContext.Properties["user"] = userName;
- log.Info("This log message has a LogicalThreadContext Property called 'user'");
-
-
- using(LogicalThreadContext.Stacks["LDC"].Push("my context message"))
- {
- log.Info("This log message has a LogicalThreadContext Stack message that includes 'my context message'");
-
- } // at the end of the using block the message is automatically popped
-
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.Info("Application Start");
- log.Debug("This is a debug message");
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is another debug message");
- }
-
-
- using(NDC.Push("my context message"))
- {
- ... all log calls will have 'my context message' included ...
-
- } // at the end of the using block the message is automatically removed
-
-
- using(log4net.NDC.Push("NDC_Message"))
- {
- log.Warn("This should have an NDC message");
- }
-
-
- var someValue = "ExampleContext"
- using(log4net.NDC.PushFormat("NDC_Message {0}", someValue))
- {
- log.Warn("This should have an NDC message");
- }
-
- -
-
-
-
null - -"(null)" -
- -
-
- -- For a one dimensional array this is the - array type name, an open brace, followed by a comma - separated list of the elements (using the appropriate - renderer), followed by a close brace. - -- For example: -int[] {1, 2, 3} . -- If the array is not one dimensional the - -Array.ToString() is returned. -
- -
-
, & - -- Rendered as an open brace, followed by a comma - separated list of the elements (using the appropriate - renderer), followed by a close brace. - -- For example: -{a, b, c} . -- All collection classes that implement -its subclasses, - or generic equivalents all implement the interface. -
- -
-
- -- Rendered as the key, an equals sign ('='), and the value (using the appropriate - renderer). - -- For example: -key=value . -
- -
-
other -- -Object.ToString()
-
-
-
-
-
No entry for the potential parent of -exists - We create a ProvisionNode for this potential - parent and insert -in that provision node. -
- -
-
The entry is of type Logger for the potential parent. -- The entry is -'s nearest existing parent. We - update 's parent field with this entry. We also break from - he loop because updating our parent's parent is our parent's - responsibility. -
- -
-
The entry is of type ProvisionNode for this potential parent. -- We add -to the list of children for this - potential parent. -
-
- ThreadContext.Properties["user"] = userName;
- log.Info("This log message has a ThreadContext Property called 'user'");
-
-
- using(ThreadContext.Stacks["NDC"].Push("my context message"))
- {
- log.Info("This log message has a ThreadContext Stack message that includes 'my context message'");
-
- } // at the end of the using block the message is automatically popped
-
-
- using log4net.Util;
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.InfoExt("Application Start");
- log.DebugExt("This is a debug message");
-
-
- using(log4net.LogicalThreadContext.Stacks["NDC"].Push("Stack_Message"))
- {
- log.Warn("This should have an ThreadContext Stack message");
- }
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- string s = OptionConverter.SubstituteVariables("Value of key is ${key}.");
-
-
- string s = OptionConverter.SubstituteVariables("Value of nonExistentKey is [${nonExistentKey}]");
-
-
- {key1=value1, key2=value2, key3=value3}
-
-
- {key1=value1, key2=value2, key3=value3}
-
- -
-
-
-
appdomain -- -- Used to output the friendly name of the current AppDomain. - -
- -
-
appsetting -- -- Used to output the value of a specific appSetting key in the application - configuration file. - -
- -
-
date -- -- Used to output the current date and time in the local time zone. - To output the date in universal time use the -%utcdate pattern. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %date{HH:mm:ss,fff} or - %date{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed (). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %date{ISO8601} or %date{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
env -- -- Used to output the a specific environment variable. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %env{COMPUTERNAME} would include the value - of the -COMPUTERNAME environment variable. -- The -env pattern is not supported on the .NET Compact Framework. -
- -
-
identity -- -- Used to output the user name for the currently active user - (Principal.Identity.Name). - -
- -
-
newline -- -- Outputs the platform dependent line separator character or - characters. - -- This conversion pattern name offers the same performance as using - non-portable line separator strings such as "\n", or "\r\n". - Thus, it is the preferred way of specifying a line separator. - -
- -
-
processid -- -- Used to output the system process ID for the current process. - -
- -
-
property -- -- Used to output a specific context property. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %property{user} would include the value - from the property that is keyed by the string 'user'. Each property value - that is to be included in the log must be specified separately. - Properties are stored in logging contexts. By default - the -log4net:HostName property is set to the name of machine on - which the event was originally logged. -- If no key is specified, e.g. %property then all the keys and their - values are printed in a comma separated list. - -- The properties of an event are combined from a number of different - contexts. These are listed below in the order in which they are searched. - --
-
-
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
- -
-
-
-
random -- -- Used to output a random string of characters. The string is made up of - uppercase letters and numbers. By default the string is 4 characters long. - The length of the string can be specified within braces directly following the - pattern specifier, e.g. %random{8} would output an 8 character string. - -
- -
-
username -- -- Used to output the WindowsIdentity for the currently - active user. - -
- -
-
utcdate -- -- Used to output the date of the logging event in universal time. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %utcdate{HH:mm:ss,fff} or - %utcdate{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed ( -). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %utcdate{ISO8601} or %utcdate{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
% -- -- The sequence %% outputs a single percent sign. - -
-
-
-
-
-
ISO8601 -- Uses the -formatter. - Formats using the "yyyy-MM-dd HH:mm:ss,fff" pattern. -
- -
-
DATE -- Uses the -formatter. - Formats using the "dd MMM yyyy HH:mm:ss,fff" for example,"06 Nov 1994 15:49:37,459" . -
- -
-
ABSOLUTE -- Uses the -formatter. - Formats using the "HH:mm:ss,fff" for example,"15:49:37,459" . -
- -
-
other -- Any other pattern string uses the -formatter. - This formatter passes the pattern string to the - method. - For details on valid patterns see - DateTimeFormatInfo Class. -
-
-
-
-
-
DOS -DOS or Windows line terminator -"\r\n"
- -
-
UNIX -UNIX line terminator -"\n"
-
- using(log4net.ThreadContext.Stacks["NDC"].Push("Stack_Message"))
- {
- log.Warn("This should have an ThreadContext Stack message");
- }
-
-
- CREATE TABLE [dbo].[Log] (
- [ID] [int] IDENTITY (1, 1) NOT NULL ,
- [Date] [datetime] NOT NULL ,
- [Thread] [varchar] (255) NOT NULL ,
- [Level] [varchar] (20) NOT NULL ,
- [Logger] [varchar] (255) NOT NULL ,
- [Message] [varchar] (4000) NOT NULL
- ) ON [PRIMARY]
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- "DSN=MS Access Database;UID=admin;PWD=;SystemDB=C:\data\System.mdw;SafeTransactions = 0;FIL=MS Access;DriverID = 25;DBQ=C:\data\train33.mdb"
- "Driver={Microsoft Access Driver (*.mdb)};DBQ=C:\Work\cvs_root\log4net-1.2\access.mdb;UID=;PWD=;"
- "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Work\cvs_root\log4net-1.2\access.mdb;User Id=;Password=;"
- System.Data.OleDb.OleDbConnection, System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- System.Data.SqlClient.SqlConnection, System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- Microsoft.Data.Odbc.OdbcConnection,Microsoft.Data.Odbc,version=1.0.3300.0,publicKeyToken=b77a5c561934e089,culture=neutral
- This is an optional package that you can download from
- http://msdn.microsoft.com/downloads
- search for ODBC .NET Data Provider.
- System.Data.OracleClient.OracleConnection, System.Data.OracleClient, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- This is an optional package that you can download from
- http://msdn.microsoft.com/downloads
- search for .NET Managed Provider for Oracle.
-
-
-
-
-
-
- -
-
Blue
- Green
- Red
- White
- Yellow
- Purple
- Cyan
-
-
-
Bright foreground is brighter
- Dim foreground is dimmer
- Underscore message is underlined
- Blink foreground is blinking (does not work on all terminals)
- Reverse foreground and background are reversed
- Hidden output is hidden
- Strikethrough message has a line through it
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
- -
-
- Calls -and checks that - it returns true .
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
- -
-
- Calls -and checks that - it returns true .
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
-
-
-
-
-
The cyclic buffer is full and this appender is - marked as not lossy (see -)
- -
-
An -is set and - it is triggered for the - specified.
-
-
-
-
-
-
-
-
-
-
-
-
-
- -
-
-
-
Send a message to a user account on the local machine -- -- -= <name of the local machine> - - -= <user name> -
- -
-
Send a message to a user account on a remote machine -- -- -= <name of the remote machine> - - -= <user name> -
- -
-
Send a message to a domain user account -- -- -= <name of a domain controller | uninitialized> - - -= <user name> -
- -
-
Send a message to all the names in a workgroup or domain -- -- -= <workgroup name | domain name>* -
- -
-
Send a message from the local machine to a remote machine -- -- -= <name of the local machine | uninitialized> - - -= <name of the remote machine> -
-
-
-
-
- -
-
-
-
Windows NT -- -- No special group membership is required to send a network message. - -- Admin, Accounts, Print, or Server Operator group membership is required to - successfully send a network message on a remote server. - -
- -
-
Windows 2000 or later -- -- If you send a message on a domain controller that is running Active Directory, - access is allowed or denied based on the access control list (ACL) for the securable - object. The default ACL permits only Domain Admins and Account Operators to send a network message. - -- On a member server or workstation, only Administrators and Server Operators can send a network message. - -
-
-
-
- Attach date pattern for current log file
- Backup number increments for newer files
- Infinite number of backups by file size
-
-
- determine curSizeRollBackups (only within the current roll point) -
- initiates a roll over if needed for crossing a date boundary since the last run. -
- The Compact Framework does not support the
- IPEndPoint remoteEndPoint = new IPEndPoint(IPAddress.Any, 0);
- UdpClient udpClient;
- byte[] buffer;
- string loggingEvent;
-
- try
- {
- udpClient = new UdpClient(8080);
-
- while(true)
- {
- buffer = udpClient.Receive(ref remoteEndPoint);
- loggingEvent = System.Text.Encoding.Unicode.GetString(buffer);
- Console.WriteLine(loggingEvent);
- }
- }
- catch(Exception e)
- {
- Console.WriteLine(e.ToString());
- }
-
-
- Dim remoteEndPoint as IPEndPoint
- Dim udpClient as UdpClient
- Dim buffer as Byte()
- Dim loggingEvent as String
-
- Try
- remoteEndPoint = new IPEndPoint(IPAddress.Any, 0)
- udpClient = new UdpClient(8080)
-
- While True
- buffer = udpClient.Receive(ByRef remoteEndPoint)
- loggingEvent = System.Text.Encoding.Unicode.GetString(buffer)
- Console.WriteLine(loggingEvent)
- Wend
- Catch e As Exception
- Console.WriteLine(e.ToString())
- End Try
-
-
-
-
-
- -
-
-
-
224.0.0.1 -- -- Sends a message to all system on the subnet. - -
- -
-
224.0.0.2 -- -- Sends a message to all routers on the subnet. - -
- -
-
224.0.0.12 -- -- The DHCP server answers messages on the IP address 224.0.0.12, but only on a subnet. - -
-
-
-
-
-
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- XmlConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
- -
-
-
-
-
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
-
-
-
-
-
Less than zero -This instance is less than -.
- -
-
Zero -This instance is equal to -.
- -
-
Greater than zero -- -This instance is greater than -. -or- -is .
-
-
-
-
-
Less than zero -is less than .
- -
-
Zero -is equal to .
- -
-
Greater than zero -is greater than .
-
-
-
-
-
WindowsIdentity.GetCurrent() 10000 loops, 00:00:00.2031250 seconds -
- -
-
WindowsIdentity.GetCurrent().Name 10000 loops, 00:00:08.0468750 seconds -
-
-
-
-
-
this events properties -- This event has -that can be set. These - properties are specific to this event only. -
- -
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
-
-
-
-
DEBUG -- The -and methods log messages - at the DEBUG level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
INFO -- The -and methods log messages - at the INFO level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
WARN -- The -and methods log messages - at the WARN level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
ERROR -- The -and methods log messages - at the ERROR level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
FATAL -- The -and methods log messages - at the FATAL level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
-
- log.Debug("This is entry number: " + i );
-
-
- if (log.IsDebugEnabled())
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- GlobalContext.Properties["hostname"] = Environment.MachineName;
-
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.Info("Application Start");
- log.Debug("This is a debug message");
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is another debug message");
- }
-
-
- log.Debug("This is entry number: " + i );
-
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- private static readonly bool isDebugEnabled = log.IsDebugEnabled;
-
-
- if (isDebugEnabled)
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- StringWriter writer = new StringWriter();
- Layout.Format(writer, loggingEvent);
- string formattedEvent = writer.ToString();
-
-
- ILog log = LogManager.GetLogger(typeof(TestApp));
- log.Debug("Message 1");
- log.Warn("Message 2");
-
-
- DEBUG [main]: Message 1
- WARN [main]: Message 2
-
- -
-
-
-
a -Equivalent to appdomain -
- -
-
appdomain -- Used to output the friendly name of the AppDomain where the - logging event was generated. - -
- -
-
aspnet-cache -- -- Used to output all cache items in the case of %aspnet-cache or just one named item if used as %aspnet-cache{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-context -- -- Used to output all context items in the case of %aspnet-context or just one named item if used as %aspnet-context{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-request -- -- Used to output all request parameters in the case of %aspnet-request or just one named param if used as %aspnet-request{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-session -- -- Used to output all session items in the case of %aspnet-session or just one named item if used as %aspnet-session{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
c -Equivalent to logger -
- -
-
C -Equivalent to type -
- -
-
class -Equivalent to type -
- -
-
d -Equivalent to date -
- -
-
date -- -- Used to output the date of the logging event in the local time zone. - To output the date in universal time use the -%utcdate pattern. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %date{HH:mm:ss,fff} or - %date{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed (). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %date{ISO8601} or %date{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
exception -- -- Used to output the exception passed in with the log message. - -- If an exception object is stored in the logging event - it will be rendered into the pattern output with a - trailing newline. - If there is no exception then nothing will be output - and no trailing newline will be appended. - It is typical to put a newline before the exception - and to have the exception as the last data in the pattern. - -
- -
-
F -Equivalent to file -
- -
-
file -- -- Used to output the file name where the logging request was - issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
identity -- -- Used to output the user name for the currently active user - (Principal.Identity.Name). - -- WARNING Generating caller information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -
- -
-
l -Equivalent to location -
- -
-
L -Equivalent to line -
- -
-
location -- -- Used to output location information of the caller which generated - the logging event. - -- The location information depends on the CLI implementation but - usually consists of the fully qualified name of the calling - method followed by the callers source the file name and line - number between parentheses. - -- The location information can be very useful. However, its - generation is extremely slow. Its use should be avoided - unless execution speed is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
level -- -- Used to output the level of the logging event. - -
- -
-
line -- -- Used to output the line number from where the logging request - was issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
logger -- -- Used to output the logger of the logging event. The - logger conversion specifier can be optionally followed by - precision specifier, that is a decimal constant in - brackets. - -- If a precision specifier is given, then only the corresponding - number of right most components of the logger name will be - printed. By default the logger name is printed in full. - -- For example, for the logger name "a.b.c" the pattern - %logger{2} will output "b.c". - -
- -
-
m -Equivalent to message -
- -
-
M -Equivalent to method -
- -
-
message -- -- Used to output the application supplied message associated with - the logging event. - -
- -
-
mdc -- -- The MDC (old name for the ThreadContext.Properties) is now part of the - combined event properties. This pattern is supported for compatibility - but is equivalent to property. - -
- -
-
method -- -- Used to output the method name where the logging request was - issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
n -Equivalent to newline -
- -
-
newline -- -- Outputs the platform dependent line separator character or - characters. - -- This conversion pattern offers the same performance as using - non-portable line separator strings such as "\n", or "\r\n". - Thus, it is the preferred way of specifying a line separator. - -
- -
-
ndc -- -- Used to output the NDC (nested diagnostic context) associated - with the thread that generated the logging event. - -
- -
-
p -Equivalent to level -
- -
-
P -Equivalent to property -
- -
-
properties -Equivalent to property -
- -
-
property -- -- Used to output the an event specific property. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %property{user} would include the value - from the property that is keyed by the string 'user'. Each property value - that is to be included in the log must be specified separately. - Properties are added to events by loggers or appenders. By default - the -log4net:HostName property is set to the name of machine on - which the event was originally logged. -- If no key is specified, e.g. %property then all the keys and their - values are printed in a comma separated list. - -- The properties of an event are combined from a number of different - contexts. These are listed below in the order in which they are searched. - --
-
-
-
the event properties -- The event has -that can be set. These - properties are specific to this event only. -
- -
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
- -
-
-
-
r -Equivalent to timestamp -
- -
-
stacktrace -- -- Used to output the stack trace of the logging event - The stack trace level specifier may be enclosed - between braces. For example, %stacktrace{level}. - If no stack trace level specifier is given then 1 is assumed - -- Output uses the format: - type3.MethodCall3 > type2.MethodCall2 > type1.MethodCall1 - -- This pattern is not available for Compact Framework assemblies. - -
- -
-
stacktracedetail -- -- Used to output the stack trace of the logging event - The stack trace level specifier may be enclosed - between braces. For example, %stacktracedetail{level}. - If no stack trace level specifier is given then 1 is assumed - -- Output uses the format: - type3.MethodCall3(type param,...) > type2.MethodCall2(type param,...) > type1.MethodCall1(type param,...) - -- This pattern is not available for Compact Framework assemblies. - -
- -
-
t -Equivalent to thread -
- -
-
timestamp -- -- Used to output the number of milliseconds elapsed since the start - of the application until the creation of the logging event. - -
- -
-
thread -- -- Used to output the name of the thread that generated the - logging event. Uses the thread number if no name is available. - -
- -
-
type -- -- Used to output the fully qualified type name of the caller - issuing the logging request. This conversion specifier - can be optionally followed by precision specifier, that - is a decimal constant in brackets. - -- If a precision specifier is given, then only the corresponding - number of right most components of the class name will be - printed. By default the class name is output in fully qualified form. - -- For example, for the class name "log4net.Layout.PatternLayout", the - pattern %type{1} will output "PatternLayout". - -- WARNING Generating the caller class information is - slow. Thus, its use should be avoided unless execution speed is - not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
u -Equivalent to identity -
- -
-
username -- -- Used to output the WindowsIdentity for the currently - active user. - -- WARNING Generating caller WindowsIdentity information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -
- -
-
utcdate -- -- Used to output the date of the logging event in universal time. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %utcdate{HH:mm:ss,fff} or - %utcdate{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed ( -). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %utcdate{ISO8601} or %utcdate{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
w -Equivalent to username -
- -
-
x -Equivalent to ndc -
- -
-
X -Equivalent to mdc -
- -
-
% -- -- The sequence %% outputs a single percent sign. - -
-
-
-
-
- | Format modifier | -left justify | -minimum width | -maximum width | -comment | -
|---|---|---|---|---|
| %20logger | -false | -20 | -none | -
- |
-
| %-20logger | -true | -20 | -none | -
- |
-
| %.30logger | -NA | -none | -30 | -
- |
-
| false | -20 | -30 | -
- |
- |
| %-20.30logger | -true | -20 | -30 | -
- |
-
- The following patterns
%timestamp [%thread] %level %logger %ndc - %message%newline
- %-6timestamp [%15.15thread] %-5level %30.30logger %ndc - %message%newline
- -
-
-
-
ISO8601 -- Uses the -formatter. - Formats using the "yyyy-MM-dd HH:mm:ss,fff" pattern. -
- -
-
DATE -- Uses the -formatter. - Formats using the "dd MMM yyyy HH:mm:ss,fff" for example,"06 Nov 1994 15:49:37,459" . -
- -
-
ABSOLUTE -- Uses the -formatter. - Formats using the "HH:mm:ss,yyyy" for example,"15:49:37,459" . -
- -
-
other -- Any other pattern string uses the -formatter. - This formatter passes the pattern string to the - method. - For details on valid patterns see - DateTimeFormatInfo Class. -
-
-
-
-
-
Message -
- -
-
Source -
- -
-
StackTrace -
- -
-
TargetSite -
- -
-
HelpLink -
-
- DEBUG - Hello world
-
-
- <?xml version="1.0" ?>
-
- <!DOCTYPE log4net:events SYSTEM "log4net-events.dtd" [<!ENTITY data SYSTEM "abc">]>
-
- <log4net:events version="1.2" xmlns:log4net="http://logging.apache.org/log4net/schemas/log4net-events-1.2>
- &data;
- </log4net:events>
-
-
- LogicalThreadContext.Properties["user"] = userName;
- log.Info("This log message has a LogicalThreadContext Property called 'user'");
-
-
- using(LogicalThreadContext.Stacks["LDC"].Push("my context message"))
- {
- log.Info("This log message has a LogicalThreadContext Stack message that includes 'my context message'");
-
- } // at the end of the using block the message is automatically popped
-
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.Info("Application Start");
- log.Debug("This is a debug message");
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is another debug message");
- }
-
-
- using(NDC.Push("my context message"))
- {
- ... all log calls will have 'my context message' included ...
-
- } // at the end of the using block the message is automatically removed
-
-
- using(log4net.NDC.Push("NDC_Message"))
- {
- log.Warn("This should have an NDC message");
- }
-
-
- var someValue = "ExampleContext"
- using(log4net.NDC.PushFormat("NDC_Message {0}", someValue))
- {
- log.Warn("This should have an NDC message");
- }
-
- -
-
-
-
null - -"(null)" -
- -
-
- -- For a one dimensional array this is the - array type name, an open brace, followed by a comma - separated list of the elements (using the appropriate - renderer), followed by a close brace. - -- For example: -int[] {1, 2, 3} . -- If the array is not one dimensional the - -Array.ToString() is returned. -
- -
-
, & - -- Rendered as an open brace, followed by a comma - separated list of the elements (using the appropriate - renderer), followed by a close brace. - -- For example: -{a, b, c} . -- All collection classes that implement -its subclasses, - or generic equivalents all implement the interface. -
- -
-
- -- Rendered as the key, an equals sign ('='), and the value (using the appropriate - renderer). - -- For example: -key=value . -
- -
-
other -- -Object.ToString()
-
-
-
-
-
No entry for the potential parent of -exists - We create a ProvisionNode for this potential - parent and insert -in that provision node. -
- -
-
The entry is of type Logger for the potential parent. -- The entry is -'s nearest existing parent. We - update 's parent field with this entry. We also break from - he loop because updating our parent's parent is our parent's - responsibility. -
- -
-
The entry is of type ProvisionNode for this potential parent. -- We add -to the list of children for this - potential parent. -
-
- ThreadContext.Properties["user"] = userName;
- log.Info("This log message has a ThreadContext Property called 'user'");
-
-
- using(ThreadContext.Stacks["NDC"].Push("my context message"))
- {
- log.Info("This log message has a ThreadContext Stack message that includes 'my context message'");
-
- } // at the end of the using block the message is automatically popped
-
-
- using log4net.Util;
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.InfoExt("Application Start");
- log.DebugExt("This is a debug message");
-
-
- using(log4net.LogicalThreadContext.Stacks["NDC"].Push("Stack_Message"))
- {
- log.Warn("This should have an ThreadContext Stack message");
- }
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- string s = OptionConverter.SubstituteVariables("Value of key is ${key}.");
-
-
- string s = OptionConverter.SubstituteVariables("Value of nonExistentKey is [${nonExistentKey}]");
-
-
- {key1=value1, key2=value2, key3=value3}
-
-
- {key1=value1, key2=value2, key3=value3}
-
- -
-
-
-
appdomain -- -- Used to output the friendly name of the current AppDomain. - -
- -
-
appsetting -- -- Used to output the value of a specific appSetting key in the application - configuration file. - -
- -
-
date -- -- Used to output the current date and time in the local time zone. - To output the date in universal time use the -%utcdate pattern. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %date{HH:mm:ss,fff} or - %date{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed (). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %date{ISO8601} or %date{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
env -- -- Used to output the a specific environment variable. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %env{COMPUTERNAME} would include the value - of the -COMPUTERNAME environment variable. -- The -env pattern is not supported on the .NET Compact Framework. -
- -
-
identity -- -- Used to output the user name for the currently active user - (Principal.Identity.Name). - -
- -
-
newline -- -- Outputs the platform dependent line separator character or - characters. - -- This conversion pattern name offers the same performance as using - non-portable line separator strings such as "\n", or "\r\n". - Thus, it is the preferred way of specifying a line separator. - -
- -
-
processid -- -- Used to output the system process ID for the current process. - -
- -
-
property -- -- Used to output a specific context property. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %property{user} would include the value - from the property that is keyed by the string 'user'. Each property value - that is to be included in the log must be specified separately. - Properties are stored in logging contexts. By default - the -log4net:HostName property is set to the name of machine on - which the event was originally logged. -- If no key is specified, e.g. %property then all the keys and their - values are printed in a comma separated list. - -- The properties of an event are combined from a number of different - contexts. These are listed below in the order in which they are searched. - --
-
-
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
- -
-
-
-
random -- -- Used to output a random string of characters. The string is made up of - uppercase letters and numbers. By default the string is 4 characters long. - The length of the string can be specified within braces directly following the - pattern specifier, e.g. %random{8} would output an 8 character string. - -
- -
-
username -- -- Used to output the WindowsIdentity for the currently - active user. - -
- -
-
utcdate -- -- Used to output the date of the logging event in universal time. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %utcdate{HH:mm:ss,fff} or - %utcdate{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed ( -). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %utcdate{ISO8601} or %utcdate{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
% -- -- The sequence %% outputs a single percent sign. - -
-
-
-
-
-
ISO8601 -- Uses the -formatter. - Formats using the "yyyy-MM-dd HH:mm:ss,fff" pattern. -
- -
-
DATE -- Uses the -formatter. - Formats using the "dd MMM yyyy HH:mm:ss,fff" for example,"06 Nov 1994 15:49:37,459" . -
- -
-
ABSOLUTE -- Uses the -formatter. - Formats using the "HH:mm:ss,fff" for example,"15:49:37,459" . -
- -
-
other -- Any other pattern string uses the -formatter. - This formatter passes the pattern string to the - method. - For details on valid patterns see - DateTimeFormatInfo Class. -
-
-
-
-
-
DOS -DOS or Windows line terminator -"\r\n"
- -
-
UNIX -UNIX line terminator -"\n"
-
- using(log4net.ThreadContext.Stacks["NDC"].Push("Stack_Message"))
- {
- log.Warn("This should have an ThreadContext Stack message");
- }
-
-
- CREATE TABLE [dbo].[Log] (
- [ID] [int] IDENTITY (1, 1) NOT NULL ,
- [Date] [datetime] NOT NULL ,
- [Thread] [varchar] (255) NOT NULL ,
- [Level] [varchar] (20) NOT NULL ,
- [Logger] [varchar] (255) NOT NULL ,
- [Message] [varchar] (4000) NOT NULL
- ) ON [PRIMARY]
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- "DSN=MS Access Database;UID=admin;PWD=;SystemDB=C:\data\System.mdw;SafeTransactions = 0;FIL=MS Access;DriverID = 25;DBQ=C:\data\train33.mdb"
- "Driver={Microsoft Access Driver (*.mdb)};DBQ=C:\Work\cvs_root\log4net-1.2\access.mdb;UID=;PWD=;"
- "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Work\cvs_root\log4net-1.2\access.mdb;User Id=;Password=;"
- System.Data.OleDb.OleDbConnection, System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- System.Data.SqlClient.SqlConnection, System.Data, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- Microsoft.Data.Odbc.OdbcConnection,Microsoft.Data.Odbc,version=1.0.3300.0,publicKeyToken=b77a5c561934e089,culture=neutral
- This is an optional package that you can download from
- http://msdn.microsoft.com/downloads
- search for ODBC .NET Data Provider.
- System.Data.OracleClient.OracleConnection, System.Data.OracleClient, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
- This is an optional package that you can download from
- http://msdn.microsoft.com/downloads
- search for .NET Managed Provider for Oracle.
-
-
-
-
-
-
- -
-
Blue
- Green
- Red
- White
- Yellow
- Purple
- Cyan
-
-
-
Bright foreground is brighter
- Dim foreground is dimmer
- Underscore message is underlined
- Blink foreground is blinking (does not work on all terminals)
- Reverse foreground and background are reversed
- Hidden output is hidden
- Strikethrough message has a line through it
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
- -
-
- Calls -and checks that - it returns true .
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
- -
-
- Calls -and checks that - it returns true .
-
-
-
-
-
- Checks that the severity of the -- is greater than or equal to the of this - appender.
- -
-
- Checks that the -chain accepts the - . -
-
-
-
-
-
The cyclic buffer is full and this appender is - marked as not lossy (see -)
- -
-
An -is set and - it is triggered for the - specified.
-
-
-
-
-
-
- -
-
Blue
- Green
- Red
- White
- Yellow
- Purple
- Cyan
- HighIntensity
-
-
-
-
-
-
-
-
-
-
-
-
-
- -
-
-
-
Send a message to a user account on the local machine -- -- -= <name of the local machine> - - -= <user name> -
- -
-
Send a message to a user account on a remote machine -- -- -= <name of the remote machine> - - -= <user name> -
- -
-
Send a message to a domain user account -- -- -= <name of a domain controller | uninitialized> - - -= <user name> -
- -
-
Send a message to all the names in a workgroup or domain -- -- -= <workgroup name | domain name>* -
- -
-
Send a message from the local machine to a remote machine -- -- -= <name of the local machine | uninitialized> - - -= <name of the remote machine> -
-
-
-
-
- -
-
-
-
Windows NT -- -- No special group membership is required to send a network message. - -- Admin, Accounts, Print, or Server Operator group membership is required to - successfully send a network message on a remote server. - -
- -
-
Windows 2000 or later -- -- If you send a message on a domain controller that is running Active Directory, - access is allowed or denied based on the access control list (ACL) for the securable - object. The default ACL permits only Domain Admins and Account Operators to send a network message. - -- On a member server or workstation, only Administrators and Server Operators can send a network message. - -
-
-
-
- Attach date pattern for current log file
- Backup number increments for newer files
- Infinite number of backups by file size
-
-
- determine curSizeRollBackups (only within the current roll point) -
- initiates a roll over if needed for crossing a date boundary since the last run. -
- The Compact Framework does not support the
- IPEndPoint remoteEndPoint = new IPEndPoint(IPAddress.Any, 0);
- UdpClient udpClient;
- byte[] buffer;
- string loggingEvent;
-
- try
- {
- udpClient = new UdpClient(8080);
-
- while(true)
- {
- buffer = udpClient.Receive(ref remoteEndPoint);
- loggingEvent = System.Text.Encoding.Unicode.GetString(buffer);
- Console.WriteLine(loggingEvent);
- }
- }
- catch(Exception e)
- {
- Console.WriteLine(e.ToString());
- }
-
-
- Dim remoteEndPoint as IPEndPoint
- Dim udpClient as UdpClient
- Dim buffer as Byte()
- Dim loggingEvent as String
-
- Try
- remoteEndPoint = new IPEndPoint(IPAddress.Any, 0)
- udpClient = new UdpClient(8080)
-
- While True
- buffer = udpClient.Receive(ByRef remoteEndPoint)
- loggingEvent = System.Text.Encoding.Unicode.GetString(buffer)
- Console.WriteLine(loggingEvent)
- Wend
- Catch e As Exception
- Console.WriteLine(e.ToString())
- End Try
-
-
-
-
-
- -
-
-
-
224.0.0.1 -- -- Sends a message to all system on the subnet. - -
- -
-
224.0.0.2 -- -- Sends a message to all routers on the subnet. - -
- -
-
224.0.0.12 -- -- The DHCP server answers messages on the IP address 224.0.0.12, but only on a subnet. - -
-
-
-
-
-
-
- log4net configuration XML goes here
-
-
-
-
-
-
-
-
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- XmlConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
-
-
-
-
-
-
- using log4net.Config;
- using System.IO;
- using System.Configuration;
-
- ...
-
- XmlConfigurator.Configure(new FileInfo(ConfigurationSettings.AppSettings["log4net-config-file"]));
-
-
-
-
-
-
-
- -
-
-
-
-
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
- -
-
.
-
-
-
-
-
Less than zero -This instance is less than -.
- -
-
Zero -This instance is equal to -.
- -
-
Greater than zero -- -This instance is greater than -. -or- -is .
-
-
-
-
-
Less than zero -is less than .
- -
-
Zero -is equal to .
- -
-
Greater than zero -is greater than .
-
-
-
-
-
WindowsIdentity.GetCurrent() 10000 loops, 00:00:00.2031250 seconds -
- -
-
WindowsIdentity.GetCurrent().Name 10000 loops, 00:00:08.0468750 seconds -
-
-
-
-
-
this events properties -- This event has -that can be set. These - properties are specific to this event only. -
- -
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
-
-
-
-
DEBUG -- The -and methods log messages - at the DEBUG level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
INFO -- The -and methods log messages - at the INFO level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
WARN -- The -and methods log messages - at the WARN level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
ERROR -- The -and methods log messages - at the ERROR level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
- -
-
FATAL -- The -and methods log messages - at the FATAL level. That is the level with that name defined in the - repositories. The default value - for this level is . The - property tests if this level is enabled for logging. -
-
- log.Debug("This is entry number: " + i );
-
-
- if (log.IsDebugEnabled())
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- GlobalContext.Properties["hostname"] = Environment.MachineName;
-
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.Info("Application Start");
- log.Debug("This is a debug message");
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is another debug message");
- }
-
-
- log.Debug("This is entry number: " + i );
-
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- private static readonly bool isDebugEnabled = log.IsDebugEnabled;
-
-
- if (isDebugEnabled)
- {
- log.Debug("This is entry number: " + i );
- }
-
-
- StringWriter writer = new StringWriter();
- Layout.Format(writer, loggingEvent);
- string formattedEvent = writer.ToString();
-
-
- ILog log = LogManager.GetLogger(typeof(TestApp));
- log.Debug("Message 1");
- log.Warn("Message 2");
-
-
- DEBUG [main]: Message 1
- WARN [main]: Message 2
-
- -
-
-
-
a -Equivalent to appdomain -
- -
-
appdomain -- Used to output the friendly name of the AppDomain where the - logging event was generated. - -
- -
-
aspnet-cache -- -- Used to output all cache items in the case of %aspnet-cache or just one named item if used as %aspnet-cache{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-context -- -- Used to output all context items in the case of %aspnet-context or just one named item if used as %aspnet-context{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-request -- -- Used to output all request parameters in the case of %aspnet-request or just one named param if used as %aspnet-request{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
aspnet-session -- -- Used to output all session items in the case of %aspnet-session or just one named item if used as %aspnet-session{key} - -- This pattern is not available for Compact Framework or Client Profile assemblies. - -
- -
-
c -Equivalent to logger -
- -
-
C -Equivalent to type -
- -
-
class -Equivalent to type -
- -
-
d -Equivalent to date -
- -
-
date -- -- Used to output the date of the logging event in the local time zone. - To output the date in universal time use the -%utcdate pattern. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %date{HH:mm:ss,fff} or - %date{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed (). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %date{ISO8601} or %date{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
exception -- -- Used to output the exception passed in with the log message. - -- If an exception object is stored in the logging event - it will be rendered into the pattern output with a - trailing newline. - If there is no exception then nothing will be output - and no trailing newline will be appended. - It is typical to put a newline before the exception - and to have the exception as the last data in the pattern. - -
- -
-
F -Equivalent to file -
- -
-
file -- -- Used to output the file name where the logging request was - issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
identity -- -- Used to output the user name for the currently active user - (Principal.Identity.Name). - -- WARNING Generating caller information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -
- -
-
l -Equivalent to location -
- -
-
L -Equivalent to line -
- -
-
location -- -- Used to output location information of the caller which generated - the logging event. - -- The location information depends on the CLI implementation but - usually consists of the fully qualified name of the calling - method followed by the callers source the file name and line - number between parentheses. - -- The location information can be very useful. However, its - generation is extremely slow. Its use should be avoided - unless execution speed is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
level -- -- Used to output the level of the logging event. - -
- -
-
line -- -- Used to output the line number from where the logging request - was issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
logger -- -- Used to output the logger of the logging event. The - logger conversion specifier can be optionally followed by - precision specifier, that is a decimal constant in - brackets. - -- If a precision specifier is given, then only the corresponding - number of right most components of the logger name will be - printed. By default the logger name is printed in full. - -- For example, for the logger name "a.b.c" the pattern - %logger{2} will output "b.c". - -
- -
-
m -Equivalent to message -
- -
-
M -Equivalent to method -
- -
-
message -- -- Used to output the application supplied message associated with - the logging event. - -
- -
-
mdc -- -- The MDC (old name for the ThreadContext.Properties) is now part of the - combined event properties. This pattern is supported for compatibility - but is equivalent to property. - -
- -
-
method -- -- Used to output the method name where the logging request was - issued. - -- WARNING Generating caller location information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
n -Equivalent to newline -
- -
-
newline -- -- Outputs the platform dependent line separator character or - characters. - -- This conversion pattern offers the same performance as using - non-portable line separator strings such as "\n", or "\r\n". - Thus, it is the preferred way of specifying a line separator. - -
- -
-
ndc -- -- Used to output the NDC (nested diagnostic context) associated - with the thread that generated the logging event. - -
- -
-
p -Equivalent to level -
- -
-
P -Equivalent to property -
- -
-
properties -Equivalent to property -
- -
-
property -- -- Used to output the an event specific property. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %property{user} would include the value - from the property that is keyed by the string 'user'. Each property value - that is to be included in the log must be specified separately. - Properties are added to events by loggers or appenders. By default - the -log4net:HostName property is set to the name of machine on - which the event was originally logged. -- If no key is specified, e.g. %property then all the keys and their - values are printed in a comma separated list. - -- The properties of an event are combined from a number of different - contexts. These are listed below in the order in which they are searched. - --
-
-
-
the event properties -- The event has -that can be set. These - properties are specific to this event only. -
- -
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
- -
-
-
-
r -Equivalent to timestamp -
- -
-
stacktrace -- -- Used to output the stack trace of the logging event - The stack trace level specifier may be enclosed - between braces. For example, %stacktrace{level}. - If no stack trace level specifier is given then 1 is assumed - -- Output uses the format: - type3.MethodCall3 > type2.MethodCall2 > type1.MethodCall1 - -- This pattern is not available for Compact Framework assemblies. - -
- -
-
stacktracedetail -- -- Used to output the stack trace of the logging event - The stack trace level specifier may be enclosed - between braces. For example, %stacktracedetail{level}. - If no stack trace level specifier is given then 1 is assumed - -- Output uses the format: - type3.MethodCall3(type param,...) > type2.MethodCall2(type param,...) > type1.MethodCall1(type param,...) - -- This pattern is not available for Compact Framework assemblies. - -
- -
-
t -Equivalent to thread -
- -
-
timestamp -- -- Used to output the number of milliseconds elapsed since the start - of the application until the creation of the logging event. - -
- -
-
thread -- -- Used to output the name of the thread that generated the - logging event. Uses the thread number if no name is available. - -
- -
-
type -- -- Used to output the fully qualified type name of the caller - issuing the logging request. This conversion specifier - can be optionally followed by precision specifier, that - is a decimal constant in brackets. - -- If a precision specifier is given, then only the corresponding - number of right most components of the class name will be - printed. By default the class name is output in fully qualified form. - -- For example, for the class name "log4net.Layout.PatternLayout", the - pattern %type{1} will output "PatternLayout". - -- WARNING Generating the caller class information is - slow. Thus, its use should be avoided unless execution speed is - not an issue. - -- See the note below on the availability of caller location information. - -
- -
-
u -Equivalent to identity -
- -
-
username -- -- Used to output the WindowsIdentity for the currently - active user. - -- WARNING Generating caller WindowsIdentity information is - extremely slow. Its use should be avoided unless execution speed - is not an issue. - -
- -
-
utcdate -- -- Used to output the date of the logging event in universal time. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %utcdate{HH:mm:ss,fff} or - %utcdate{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed ( -). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %utcdate{ISO8601} or %utcdate{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
w -Equivalent to username -
- -
-
x -Equivalent to ndc -
- -
-
X -Equivalent to mdc -
- -
-
% -- -- The sequence %% outputs a single percent sign. - -
-
-
-
-
- | Format modifier | -left justify | -minimum width | -maximum width | -comment | -
|---|---|---|---|---|
| %20logger | -false | -20 | -none | -
- |
-
| %-20logger | -true | -20 | -none | -
- |
-
| %.30logger | -NA | -none | -30 | -
- |
-
| false | -20 | -30 | -
- |
- |
| %-20.30logger | -true | -20 | -30 | -
- |
-
- The following patterns
%timestamp [%thread] %level %logger %ndc - %message%newline
- %-6timestamp [%15.15thread] %-5level %30.30logger %ndc - %message%newline
- -
-
-
-
ISO8601 -- Uses the -formatter. - Formats using the "yyyy-MM-dd HH:mm:ss,fff" pattern. -
- -
-
DATE -- Uses the -formatter. - Formats using the "dd MMM yyyy HH:mm:ss,fff" for example,"06 Nov 1994 15:49:37,459" . -
- -
-
ABSOLUTE -- Uses the -formatter. - Formats using the "HH:mm:ss,yyyy" for example,"15:49:37,459" . -
- -
-
other -- Any other pattern string uses the -formatter. - This formatter passes the pattern string to the - method. - For details on valid patterns see - DateTimeFormatInfo Class. -
-
-
-
-
-
Message -
- -
-
Source -
- -
-
StackTrace -
- -
-
TargetSite -
- -
-
HelpLink -
-
- DEBUG - Hello world
-
-
- <?xml version="1.0" ?>
-
- <!DOCTYPE log4net:events SYSTEM "log4net-events.dtd" [<!ENTITY data SYSTEM "abc">]>
-
- <log4net:events version="1.2" xmlns:log4net="http://logging.apache.org/log4net/schemas/log4net-events-1.2>
- &data;
- </log4net:events>
-
-
- LogicalThreadContext.Properties["user"] = userName;
- log.Info("This log message has a LogicalThreadContext Property called 'user'");
-
-
- using(LogicalThreadContext.Stacks["LDC"].Push("my context message"))
- {
- log.Info("This log message has a LogicalThreadContext Stack message that includes 'my context message'");
-
- } // at the end of the using block the message is automatically popped
-
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.Info("Application Start");
- log.Debug("This is a debug message");
-
- if (log.IsDebugEnabled)
- {
- log.Debug("This is another debug message");
- }
-
-
- using(NDC.Push("my context message"))
- {
- ... all log calls will have 'my context message' included ...
-
- } // at the end of the using block the message is automatically removed
-
-
- using(log4net.NDC.Push("NDC_Message"))
- {
- log.Warn("This should have an NDC message");
- }
-
-
- var someValue = "ExampleContext"
- using(log4net.NDC.PushFormat("NDC_Message {0}", someValue))
- {
- log.Warn("This should have an NDC message");
- }
-
- -
-
-
-
null - -"(null)" -
- -
-
- -- For a one dimensional array this is the - array type name, an open brace, followed by a comma - separated list of the elements (using the appropriate - renderer), followed by a close brace. - -- For example: -int[] {1, 2, 3} . -- If the array is not one dimensional the - -Array.ToString() is returned. -
- -
-
, & - -- Rendered as an open brace, followed by a comma - separated list of the elements (using the appropriate - renderer), followed by a close brace. - -- For example: -{a, b, c} . -- All collection classes that implement -its subclasses, - or generic equivalents all implement the interface. -
- -
-
- -- Rendered as the key, an equals sign ('='), and the value (using the appropriate - renderer). - -- For example: -key=value . -
- -
-
other -- -Object.ToString()
-
-
-
-
-
No entry for the potential parent of -exists - We create a ProvisionNode for this potential - parent and insert -in that provision node. -
- -
-
The entry is of type Logger for the potential parent. -- The entry is -'s nearest existing parent. We - update 's parent field with this entry. We also break from - he loop because updating our parent's parent is our parent's - responsibility. -
- -
-
The entry is of type ProvisionNode for this potential parent. -- We add -to the list of children for this - potential parent. -
-
- ThreadContext.Properties["user"] = userName;
- log.Info("This log message has a ThreadContext Property called 'user'");
-
-
- using(ThreadContext.Stacks["NDC"].Push("my context message"))
- {
- log.Info("This log message has a ThreadContext Stack message that includes 'my context message'");
-
- } // at the end of the using block the message is automatically popped
-
-
- using log4net.Util;
-
- ILog log = LogManager.GetLogger("application-log");
-
- log.InfoExt("Application Start");
- log.DebugExt("This is a debug message");
-
-
- using(log4net.LogicalThreadContext.Stacks["NDC"].Push("Stack_Message"))
- {
- log.Warn("This should have an ThreadContext Stack message");
- }
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- string s = OptionConverter.SubstituteVariables("Value of key is ${key}.");
-
-
- string s = OptionConverter.SubstituteVariables("Value of nonExistentKey is [${nonExistentKey}]");
-
-
- {key1=value1, key2=value2, key3=value3}
-
-
- {key1=value1, key2=value2, key3=value3}
-
- -
-
-
-
appdomain -- -- Used to output the friendly name of the current AppDomain. - -
- -
-
appsetting -- -- Used to output the value of a specific appSetting key in the application - configuration file. - -
- -
-
date -- -- Used to output the current date and time in the local time zone. - To output the date in universal time use the -%utcdate pattern. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %date{HH:mm:ss,fff} or - %date{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed (). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %date{ISO8601} or %date{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
env -- -- Used to output the a specific environment variable. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %env{COMPUTERNAME} would include the value - of the -COMPUTERNAME environment variable. -- The -env pattern is not supported on the .NET Compact Framework. -
- -
-
identity -- -- Used to output the user name for the currently active user - (Principal.Identity.Name). - -
- -
-
newline -- -- Outputs the platform dependent line separator character or - characters. - -- This conversion pattern name offers the same performance as using - non-portable line separator strings such as "\n", or "\r\n". - Thus, it is the preferred way of specifying a line separator. - -
- -
-
processid -- -- Used to output the system process ID for the current process. - -
- -
-
property -- -- Used to output a specific context property. The key to - lookup must be specified within braces and directly following the - pattern specifier, e.g. %property{user} would include the value - from the property that is keyed by the string 'user'. Each property value - that is to be included in the log must be specified separately. - Properties are stored in logging contexts. By default - the -log4net:HostName property is set to the name of machine on - which the event was originally logged. -- If no key is specified, e.g. %property then all the keys and their - values are printed in a comma separated list. - -- The properties of an event are combined from a number of different - contexts. These are listed below in the order in which they are searched. - --
-
-
-
the thread properties -- The -that are set on the current - thread. These properties are shared by all events logged on this thread. -
- -
-
the global properties -- The -that are set globally. These - properties are shared by all the threads in the AppDomain. -
-
- -
-
-
-
random -- -- Used to output a random string of characters. The string is made up of - uppercase letters and numbers. By default the string is 4 characters long. - The length of the string can be specified within braces directly following the - pattern specifier, e.g. %random{8} would output an 8 character string. - -
- -
-
username -- -- Used to output the WindowsIdentity for the currently - active user. - -
- -
-
utcdate -- -- Used to output the date of the logging event in universal time. - The date conversion - specifier may be followed by a date format specifier enclosed - between braces. For example, %utcdate{HH:mm:ss,fff} or - %utcdate{dd MMM yyyy HH:mm:ss,fff}. If no date format specifier is - given then ISO8601 format is - assumed ( -). - - The date format specifier admits the same syntax as the - time pattern string of the -. - - For better results it is recommended to use the log4net date - formatters. These can be specified using one of the strings - "ABSOLUTE", "DATE" and "ISO8601" for specifying - -, - and respectively - . For example, - %utcdate{ISO8601} or %utcdate{ABSOLUTE}. - - These dedicated date formatters perform significantly - better than -. -
- -
-
% -- -- The sequence %% outputs a single percent sign. - -
-
-
-
-
-
ISO8601 -- Uses the -formatter. - Formats using the "yyyy-MM-dd HH:mm:ss,fff" pattern. -
- -
-
DATE -- Uses the -formatter. - Formats using the "dd MMM yyyy HH:mm:ss,fff" for example,"06 Nov 1994 15:49:37,459" . -
- -
-
ABSOLUTE -- Uses the -formatter. - Formats using the "HH:mm:ss,fff" for example,"15:49:37,459" . -
- -
-
other -- Any other pattern string uses the -formatter. - This formatter passes the pattern string to the - method. - For details on valid patterns see - DateTimeFormatInfo Class. -
-
-
-
-
-
DOS -DOS or Windows line terminator -"\r\n"
- -
-
UNIX -UNIX line terminator -"\n"
-
- using(log4net.ThreadContext.Stacks["NDC"].Push("Stack_Message"))
- {
- log.Warn("This should have an ThreadContext Stack message");
- }
-
-