common.logging

问题 Looking a project that uses Common.Logging for .NET, I noticed that some classes declare the logger instance as a class static member. For instance: public class HelloJob : IJob { private static ILog _log = LogManager.GetLogger(typeof(HelloJob)); public HelloJob() { } public virtual void Execute(IJobExecutionContext context) { _log.Info(string.Format("Hello World! - {0}", System.DateTime.Now.ToString("r"))); } } And in other classes the logger is declared as an instance member: public class

问题 As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 7 years ago . EDIT: Common.Logging 2.1.1 was released on June 9, 2012 and the Github page is fairly active, with the author commenting specifically

问题 As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 7 years ago . EDIT: Common.Logging 2.1.1 was released on June 9, 2012 and the Github page is fairly active, with the author commenting specifically

问题 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? 回答1: 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

问题 This question was asked here, however the solution was not a programmatic configuration. In this case, a library Wrapper.dll is properly configured with Common.Logging . A console application ConsoleApplication1.exe attempts to implement a Log4NetLoggerFactoryAdapter . This works fine , sending log entries from Wrapper.dll to the console. The app.config : <configSections> <sectionGroup name="common"> <section name="logging" type="Common.Logging.ConfigurationSectionHandler, Common.Logging" />

问题 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

问题 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? 回答1: 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

问题 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. 回答1: 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>

问题 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? 回答1: 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"

问题 I'm getting the following exception when I try to call var log = LogManager.GetLogger(this.GetType()); A first chance exception of type 'Common.Logging.ConfigurationException' occurred in Common.Logging.dll An unhanded exception of type 'Common.Logging.ConfigurationException' occurred in Common.Logging.dll Additional information: Failed obtaining configuration for Common.Logging from configuration section 'common/logging'. This is a .NET 4 application with references to log4net.dll Common