common.logging

I am trying to adopt Common.Logging in our application, however I am having some trouble setting it up with system.diagnostics. It works with straight up Trace, but not TraceSource. I was using Common.Logging.Simple.TraceLoggerFactoryAdapter . Do i need a different adapter for TraceSource? This is pretty late, but maybe it will still help you... According to the Common.Logging source here , the TraceLoggerFactoryAdapter does support configuring such that it uses TraceSources. The TraceLoggerFactoryAdapter has a property (that is configurable in app.config file) called "useTraceSource". If that

Does anyone know if there is an equivalent in Common.Logging (for .Net) to set properties for the log4net factory adapter? I have had great success when just using log4net by doing: <appender name="FileAppender" type="log4net.Appender.RollingFileAppender"> <file type="log4net.Util.PatternString" value="logs\Log_%property{BrokerID}.txt"/> <appendToFile value="false"/> <rollingStyle value="Size"/> <maxSizeRollBackups value="-1"/> <maximumFileSize value="50GB"/> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%date %-5level %logger - %message%newline"/> </layout> </appender

How to dynamically change the FileName using a variable from C#? My idea is to create a log file like Log_<UserId_From_DB>_${date:format=yyyy-MM-dd}.log . Any ideas? Julian Another option is to use the Global Diagnostic Context - $(GDC) : Set the value in C# GlobalDiagnosticsContext.Set("UserId_From_DB","42"); In the config (nlog.config): <target type="file" filename="Log_${gdc:item=UserId_From_DB}_${date:format=yyyy-MM-dd}.log" ..> Please avoid modifying NLog Variables at runtime (See previous answer below). They should be seen as readonly, because they are not threadsafe. NLog Variables will

I tried using these together today, and was getting a version mismatch, as it's looking for NLog v1. Does Common.Logging support NLog v2 yet? If not, does anyone know if an assembly version redirect can safely be used? You can simply do assembly redirect in app.config or web.config, and CommonLogging will just work fine with NLog2 by using NLog2 as logging framework: <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="NLog" publicKeyToken="5120e14c03d0593c" culture="neutral" /> <bindingRedirect oldVersion="1.0.0.0-2.0.0.0" newVersion

I'm trying to configure a console application with the following logging assemblies: Common.Logging.dll (2.1.0.0) Common.Logging.Log4Net1211.dll (2.1.0.0) log4net.dll (1.2.11.0) If the logger gets configured programmatically then everything works fine: NameValueCollection properties = new NameValueCollection(); properties["showDateTime"] = "true"; Common.Logging.LogManager.Adapter = new Common.Logging.Simple.ConsoleOutLoggerFactoryAdapter(properties); But if I try to launch it using the following configuration file, it blows up: <?xml version="1.0"?> <configuration> <configSections>

I'm using Quartz.net within a windows service. Currently, the trigger is not firing - I'd like to use the logging to find out why. I have edited my config file for the windows service: <configSections> <section name="log4net" type="log4net.Config.Log4NetConfigurationSectionHandler, log4net" /> <sectionGroup name="common"> <section name="logging" type="Common.Logging.ConfigurationSectionHandler, Common.Logging" /> </sectionGroup> </configSections> <appSettings> <!--specific win service settings here--> </appSettings> <common> <logging> <factoryAdapter type="Common.Logging.Log4Net

My company's standard logging tool is NLog. I'm trying to introduce Quartz.net and was asked if it could use NLog instead of Log4Net. I know I can recompile to use NLog, but I'd like to do it from the configuration files if at all possible. LeftyX Assuming that you're using Quartz.net 1.0.3. you have to add a reference to the following assemblies: Common.Logging Common.Logging.NLog NLog Then you have to add the following configuration in your application's config file: <configuration> <configSections> <sectionGroup name="common"> <section name="logging" type="Common.Logging