log4net - Framework Support

none

none

• Assembly attributes

  The .NET Compact Framework 1.0 does not support retrieving assembly-level attributes, therefore all log4net configuration attributes were removed from the .NET Compact Framwork 1.0 version of log4net.

  For Smart-device applications, the log4net system can be configured by passing the location of the log4net configuration file to the log4net.Config.DOMConfigurator.Configure(FileInfo) method in the entrypoint of the application.

  For example:

  namespace TestApp
  {
  	using System.IO;
  
  	public class EntryPoint
  	{
  		/// <summary>
  		/// Application entry point.
  		/// </summary>
  		public static void Main() 
  		{
  			// Uncomment the next line to enable log4net internal debugging
  			// log4net.helpers.LogLog.InternalDebugging = true;
  
  			// This will instruct log4net to look for a configuration file
  			// called config.log4net in the root directory of trhe device
  			log4net.Config.DOMConfigurator.Configure(new FileInfo(@"\config.log4net"));
  
  			...
  			
  			// This will shutdown the log4net system
  			log4net.LogManager.Shutdown();
  		}
  	}
  }						
  							

• Notification events

  The .NET Compact Framework 1.0 does not support notification events during the application shutdown, therefore log4net cannot automaticaly hook the application shutdown notification.

  Applications will need to programatically shutdown the log4net system during the application's shutdown using the log4net.LogManager.Shutdown() method in order to prevent losing logging events. See the code above for an example.

• FileSystemWatcher

  The .NET Compact Framework 1.0 does not support the System.IO.FileSystemWatcher class. As a result, the DOMConfiguratorAttribute.Watch property and the DOMConfigurator.ConfigureAndWatch methods are not available. Watching changes to the log4net configuration file is not supported on the .NET Compact Framework 1.0.

• UserName

  The .NET Compact Framework 1.0 does not support the System.Security.Principal.WindowsIdentity class. This is used to capture the current thread's user identity. Therefore the LoggingEvent.UserName property will return the value "NOT AVAILABLE".

• Environment variables

  The .NET Compact Framework 1.0 does not support retrieving environment variables, therefore it's not possibe to substitute environment variables in parameter values when using the .NET Compact Framework 1.0 version of log4net.

• Serialization

  The .NET Compact Framework 1.0 does not support serialization, therefore none of the log4net classes in the .NET Compact Framework 1.0 version are serializable.

• Reflection

  In Mono 0.23, the Type.GetProperty(string, BindingFlags) method does not support case-insensitive lookup of properties. This issue (Mono bug #38957) forces users to use the exact case for all dynamically bound elements in the log4net configuration file, these include:

  • Layout
  • Filter

  For example, instead of having the following section in the log4net configuration file:

  <appender name="ConsoleAppender" type="log4net.Appender.ConsoleAppender">
  	<layout type="log4net.Layout.PatternLayout">
  		<param name="ConversionPattern" value="%d [%t] %-5p %c - %m%n" />
  	</layout>
  	<filter type="log4net.Filter.LevelRangeFilter">
  		<param name="LevelMin" value="DEBUG" />
  		<param name="LevelMax" value="INFO" />
  	</filter>
  </appender>					
  							

  You should use the following section (in a Mono 0.23 applications):

  <appender name="ConsoleAppender" type="log4net.Appender.ConsoleAppender">
  	<Layout type="log4net.Layout.PatternLayout">
  		<param name="ConversionPattern" value="%d [%t] %-5p %c - %m%n" />
  	</Layout>
  	<Filter type="log4net.Filter.LevelRangeFilter">
  		<param name="LevelMin" value="DEBUG" />
  		<param name="LevelMax" value="INFO" />
  	</Filter>
  </appender>
  							

• FileSystemWatcher

  SSCLI 1.0 does not support the System.IO.FileSystemWatcher class. As a result, the DOMConfiguratorAttribute.Watch property and the DOMConfigurator.ConfigureAndWatch methods are not available. Watching changes to the log4net configuration file is not supported on SSCLI 1.0.

• UserName

  SSCLI 1.0 does not support the System.Security.Principal.WindowsIdentity class. This is used to capture the current thread's user identity. Therefore the LoggingEvent.UserName property will return the value "NOT AVAILABLE".