You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(5) |
Sep
(4) |
Oct
(2) |
Nov
|
Dec
(16) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
|
Feb
(1) |
Mar
(10) |
Apr
(4) |
May
(9) |
Jun
(37) |
Jul
(32) |
Aug
(32) |
Sep
(35) |
Oct
(22) |
Nov
(9) |
Dec
(3) |
2006 |
Jan
(8) |
Feb
(12) |
Mar
(5) |
Apr
(19) |
May
(21) |
Jun
(17) |
Jul
(41) |
Aug
(15) |
Sep
(15) |
Oct
(4) |
Nov
(1) |
Dec
(4) |
2007 |
Jan
|
Feb
|
Mar
(1) |
Apr
(3) |
May
|
Jun
(4) |
Jul
(4) |
Aug
(1) |
Sep
(9) |
Oct
(1) |
Nov
|
Dec
(2) |
2008 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
(8) |
Jul
|
Aug
|
Sep
(1) |
Oct
(3) |
Nov
(5) |
Dec
|
2009 |
Jan
(11) |
Feb
(5) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(1) |
Sep
(2) |
Oct
(1) |
Nov
(3) |
Dec
(4) |
2010 |
Jan
|
Feb
(6) |
Mar
(2) |
Apr
(2) |
May
(9) |
Jun
(7) |
Jul
|
Aug
(2) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Jake M. <jac...@ya...> - 2013-06-17 14:35:09
|
http://www.cpsystems.com.au/mtczvi/lhmgl/dqwij/tkj/lynmph/apu.html Jake Milnes ohqy/div> |
From: Andrew S. <ma...@an...> - 2011-06-22 09:01:54
|
Hi, If you are upgrading custom targets from NLog 1.x to 2.x you may bump into a breaking change which is not very clear from just reading posts on the wiki. As far as I can tell the functionality to resolve the formatted message wasCompiledLayout.GetFormattedMessage(logEvent); and now is: Layout.Render(logEvent); I spent sometime googling and these wiki pages _don't_ appear to capture this change (at least not directly) http://nlog-project.org/wiki/List_of_breaking_changes_in_NLog_2.0 http://nlog-project.org/2009/10/19/nlog-2-backwards-compatibility-and-breaking-change-policy.html And it's a bit confusing because GetFormattedMessage still exists on layout but it is now marked as protected. I hope this saves someone some time. Regards, Stonie. |
From: Jarek K. <ja...@jk...> - 2010-09-27 03:20:49
|
It is my pleasure to announce that NLog 2.0 Beta 1 has been released. NLog 2.0 release is focused on adding support for new platforms (Silverlight, .NET Framework 4), improving logging architecture and manageability and addressing most frequently reported user issues. The following platforms are supported in this release: - .NET Framework 2.0 SP1 and above, 3.5 (Client and Extended profiles), 4.0 (Client and Extended profiles) - Silverlight 2.0, 3.0, 4.0 - .NET Compact Framework 2.0, 3.5 - Mono 2.x profile Read full release notes: http://nlog-project.org/nlog2-beta1-release-notes Download Beta 1 bits on CodePlex: http://nlog.codeplex.com/releases/view/52957 Source code is available on GitHub: http://github.com/jkowalski/NLog/ Bugs can be reported on CodePlex: http://nlog.codeplex.com/workitem/list/basic Discuss on forum: http://nlog-project.org/forum Subscribe to NLog RSS feed: http://nlog-project.org/feed Follow @JarekKowalski on Twitter: http://twitter.com/JarekKowalski |
From: Jarek K. <ja...@jk...> - 2010-09-03 05:08:38
|
You can also try using NLogTraceListener which was recently added to NLog 2.0: See http://bit.ly/do7nN5 for more details and example of tracing using System.Net trace source. ----- http://feeds.feedburner.com/~r/nlog/~6/2 http://feeds.feedburner.com/nlog.2.gif -- View this message in context: http://nlog-forum.1685105.n2.nabble.com/Logging-Trace-statements-tp5476229p5493990.html Sent from the NLog-list mailing list archive at Nabble.com. |
From: Jeff T. <ema...@gm...> - 2010-08-30 00:15:35
|
This appears to be asking the same question: http://nlog-project.org/forum.html#nabble-td1685596 Sounds like I need to try writing a TraceListener that logs to nlog... On Mon, Aug 30, 2010 at 10:00 AM, Jeff Tiggs < ema...@gm...> wrote: > Hi all, > > There are some very handy trace statements built into the .net framework, > see an example here: http://msdn.microsoft.com/en-us/library/ty48b824.aspx > > Is there a way I could send this trace info to nlog? I want to get it into > nlog so I can add the context info I get from the layout-renders. > > I've had a read through the documentation, and I can see there is a Trace > target. This is for getting nlog statements into Trace - which sounds like > the opposite of what I'm after. > > Thanks, > Jeff > > |
From: Jeff T. <ema...@gm...> - 2010-08-30 00:01:01
|
Hi all, There are some very handy trace statements built into the .net framework, see an example here: http://msdn.microsoft.com/en-us/library/ty48b824.aspx Is there a way I could send this trace info to nlog? I want to get it into nlog so I can add the context info I get from the layout-renders. I've had a read through the documentation, and I can see there is a Trace target. This is for getting nlog statements into Trace - which sounds like the opposite of what I'm after. Thanks, Jeff |
From: Jaroslav <jac...@gm...> - 2010-06-11 14:23:39
|
weirdest think ever... So in 1 solution I have 2 C# WinForms projects, the first one searches for ProcName1.nlog as I mentioned above and the other one doesn't and searches for ProcName2.exe.nlog!!! WTF Anybody can explain what happened and why one is acting like that and the other one oposite??? So I now have to use the 2 configs with one having the .exe... which looks awful when they don't have the same pattern. -- View this message in context: http://nlog-forum.1685105.n2.nabble.com/Error-in-documentation-and-Wiki-config-file-name-tp5152923p5168109.html Sent from the NLog-list mailing list archive at Nabble.com. |
From: Jaroslav <jac...@gm...> - 2010-06-08 14:57:58
|
sadly I must say the documentation sucks because it's incomplete... and the forum is dead as graveyard :( so there is what has been missing: NLog_InitLocal(); you have to call this before first use of Logger in native code called from managed code, you could also call NLog_ConfigureFromFile but that has been already done in managed code and would delete the entries in log files done so far (I log everything to one file from managed and native code) how I found out: I recompiled the 1.0 version from source (it wanted those old msvc?80.dll now it wants newer msvc?90.dll which I have and don't have to put them in the program folder), compiled the NLogCTest and looked what it does... wow what's that? that's not in documention nor on wiki :/ boom it works. I guess the documentation wasn't updated after some updates to the program has been made, silly. -- View this message in context: http://nlog-forum.1685105.n2.nabble.com/C-C-C-can-t-log-from-C-C-LoaderLock-tp5143973p5153757.html Sent from the NLog-list mailing list archive at Nabble.com. |
From: JackCY <jac...@gm...> - 2010-06-08 09:34:27
|
Found an error in 1.0.0.505 version of NLog documentation NLog.chm the same is on Wiki http://nlog-project.org/wiki/Configuration_file: it says: The following locations will be searched when executing a stand-alone *.exe application: - standard application configuration file (usually applicationname.exe.config) - *applicationname.exe.nlog in application's directory * - NLog.config in application's directory - NLog.dll.nlog in a directory where NLog.dll is located - file name pointed by the NLOG_GLOBAL_CONFIG_FILE environment variable (if defined) but in real it searches for (AppName.exe and NLog.dll are in the same folder): - NLog.config - *AppName.nlog* - NLog.dll.nlog So I think it doesn't search for: *applicationname.exe.nlog in application's directory *but for* **applicationname.nlog * Jaroslav* * |
From: Carlo L. <car...@gm...> - 2010-06-07 16:09:02
|
Hi All, with my colleague we created a very simple application container (that we use always in http scenario). It provides to resolve some services. One service is the Logger. For our works we needed to trace the service calls based on external sessionId. For this reason our "application container" use $(logger) as file name, so we use the sessionId as parameter for the GetLogger. It's seems to works fine! Since two days, on the same enviroment, we added a new application, based on a similiar (we changes only some session key ) application container, but some times the logs are mixed. Attention: the logs are mixed only in this newest application, the oldest it's running very well! On some files there are messages of other "logger" (other sessionId) and there is huge time span. For example: 09:19:35:876 Info Started Service1 09:19:35:876 Debug sessionId is '6502010a4c09fa49030103' 09:19:35:876 ... 09:19:35:892 Info Complete Service1 09:19:55:470 Info Started Service2 09:19:55:470 Debug sessionId is '6502010a4c09fa49030103' 09:19:55:470 ... 09:19:55:470 Info Complete Service2 *09:34:05:751 Info Started OtherService* *09:34:05:751 Debug sessionId is '6502010a4c09fdab030107' * *09:34:05:751 Debug ...* *09:34:05:751 Info Complete OtherService* How can it's possible? (I note that the old version is still working correctly in that environment and the only difference lies in SESSION_APPLICATION_KEY and different folders in which they are) Any suggestions? Best regards, Carlo This is the "application container". /// <summary> /// Application Container /// </summary> public class ApplicationContainer : IApplicationContainer { protected const string DEFAULT_LOG_FOLDER = "Logs"; protected const string DEFAULT_LOG_FOLDER_STRUCTURE = "yyyy/MM/dd/HH"; protected const string DEFAULT_LOG_LAYOUT = "${date:format=HH\\:mm\\:ss\\:fff} ${message} ${exception:format=Type,Message,StackTrace}"; protected const string SESSION_APPLICATION_KEY = "Application.Service.Key"; protected static object synch = new object(); protected static LogFactory logFactory = ConfigureLogFactory(); protected static IApplicationContainer ooc; protected Logger log; protected IMyService mySerice; /// <summary> /// The assembly to be loaded using reflection /// </summary> private static Assembly serviceActiveProvider = null; protected ApplicationContainer(string sessionId) { // Cancellation Service Provider string serviceAssemblyName = ConfigurationManager.AppSettings["Provider"]; string serviceFactoryName = ConfigurationManager.AppSettings["ProviderFactory"]; serviceActiveProvider = Assembly.Load(cancellationAssemblyName); mySerice = (IMyService)cancellationActiveProvider.CreateInstance(serviceFactoryName); /* * Set $(logger) as file name, based on sessionId if defined */ string logName = ""; lock (synch) { if ( (sessionId == null) || sessionId.Trim() == string.Empty) logName = DateTime.Now.ToString("yyyymmddHHmmssfff"); else logName = sessionId; } log = logFactory.GetLogger(logName); // Logger Injection for Cancellation Service mySerice.Logger = log; } public static IApplicationContainer GetApplication(string sessionId) { IApplicationContainer app = null; HttpContext ctx = HttpContext.Current; if (ctx == null) { /* * out-of-context; * the application container * behaves like a singleton */ if (ooc == null) ooc = new ApplicationContainer(sessionId); app = ooc; } else { /* * In a Http context; * the application container * behaves like a session-based singleton; */ if (HttpContext.Current.Session[SESSION_APPLICATION_KEY] == null) HttpContext.Current.Session[SESSION_APPLICATION_KEY] = new ApplicationContainer(sessionId); app = (IApplicationContainer)HttpContext.Current.Session[SESSION_APPLICATION_KEY]; } return app; } #region Logger Configuration & Level Definition protected static LogFactory ConfigureLogFatcory() { DateTime now = DateTime.Now; // File Configuration FileTarget fileTarget = new FileTarget(); fileTarget.CreateDirs = true; string layout = ConfigurationManager.AppSettings["LogLayout"]; if (layout == null || layout == string.Empty) layout = DEFAULT_LOG_LAYOUT; string logFolder = ConfigurationManager.AppSettings["LogFolder"]; if (logFolder == null || logFolder == string.Empty) logFolder = DEFAULT_LOG_FOLDER; string logFolderStructure = ConfigurationManager.AppSettings["LogFolderStructure"]; if (logFolderStructure == null || logFolderStructure == string.Empty) logFolderStructure = DEFAULT_LOG_FOLDER_STRUCTURE; if ( logFolder == DEFAULT_LOG_FOLDER ) fileTarget.FileName = "${basedir}/" + logFolder + "/" + now.ToString(logFolderStructure) + "/${logger}.log"; else fileTarget.FileName = logFolder + "/" + now.ToString(logFolderStructure) + "/${logger}.log"; fileTarget.KeepFileOpen = false; fileTarget.Layout = layout; LoggingConfiguration config = new LoggingConfiguration(); config.AddTarget("DefaultDSC", fileTarget); config.LoggingRules.Add(new LoggingRule("*", GetLevel(ConfigurationManager.AppSettings["LogLevel"]), fileTarget)); LogFactory factory = new LogFactory(); factory.Configuration = config; return factory; } ... #endregion #region IApplication Members public T Resolve<T>() { if (typeof(T) == typeof(Logger)) return (T)this.Resolve(typeof(T)); if (typeof(T) == typeof(IMyService)) { // Return Service return (T)this.mySerice; } throw new UnregisterServiceException(typeof(T).ToString()); } private object Resolve(Type type) { if (type == (typeof(Logger))) return this.log; return null; } #endregion #region IDisposable Members public void Dispose() { ooc = null; } #endregion } } |
From: Carlo L. <car...@gm...> - 2010-06-07 15:45:21
|
Hi All, it's possibile that LogginConfiguration.AddTarget doesn't work properly in high load scenario? Best regards. Carlo |
From: Jarek K. <ja...@jk...> - 2010-06-06 05:19:53
|
Blogged: http://nlog-project.org/2010/06/05/nlog-2-0-documentation-is-available-on-the-wiki.html Documentation for NLog 2.0 is now available on the Wiki<http://nlog-project.org/wiki/>. It includes reference documents generated automatically from code as well as hand-written documents and tutorials, some of which have been migrated from WordPress pages to the Wiki format. Documentation for targets <http://nlog-project.org/wiki/Targets>, layouts<http://nlog-project.org/wiki/Layouts>, layout renderers <http://nlog-project.org/wiki/Layout_renderers> and filters<http://nlog-project.org/wiki/Filters>has been enhanced to include usage examples which you can paste into your configuration code. Because of the new format, it is possible to enhance reference documents with user-created content, such as code or configuration samples. See documentation for the File target<http://nlog-project.org/wiki/File_target>for an example. Note that it is not possible to edit certain parts of automatically generated pages. Things like parameter list, supported platforms and usage example do not show up in Wiki source. Instead you will see a special tag which looks like: *<generatedDoc id=’File_target’ hash=’db5419b5ab45ec8defc51cb5dabeaaf4′ />**, *and causes generated doc to be inserted. The tags and contents are automatically updated whenever I re-upload documentation. Now that every piece of documentation is in Wiki format, I’m *looking for volunteers to help maintain and enhance it*, so if you like technical writing and want to own part of the documentation, please let me know. Please report any issues you find with the Wiki as comments here, or (even better), register for an account and fix those issues yourself. Jarek |
From: JackCY <jac...@gm...> - 2010-06-05 20:55:45
|
Hello, It's quite easy to get NLog working in C#, but C/C++ is much harder, there is almost no documentation, no examples, no info on web (google won't help). I have a Solution which have few C# projects .exe and .dll and one C/C++ dll, , that managed dll calls native C/C++ dll and I got it to compile with NLog, set the include, lib, but when I add first NLog_TraceA("A", "B"); to any method it tries to load the NLogC.dll and it is located correctly in the same folder as all the files of the application and NLog.dll, NLog.config, I checked with filemon that it finds the NLogC.dll, I also checked the dependencies as I had msvcm80.dll missing so it didn't load, now when it's all correct it tries to do all the stuff there when loading which is unknown to me and it crashes :( The error is:LoaderLock was detected Message: Attempting managed execution inside OS Loader lock. Do not attempt to run managed code inside a DllMain or image initialization function since doing so can cause the application to hang. My DllMain of my C/C++ dll is pure, I didn't touch it after VS generated it: // dllmain.cpp : Defines the entry point for the DLL application. #include "stdafx.h" BOOL APIENTRY DllMain( HMODULE hModule, DWORD ul_reason_for_call, LPVOID lpReserved ) { switch (ul_reason_for_call) { case DLL_PROCESS_ATTACH: case DLL_THREAD_ATTACH: case DLL_THREAD_DETACH: case DLL_PROCESS_DETACH: break; } return TRUE; } Disabling the LoaderLock warning in debug options is not an option as the application crashes with a pop window and error for the same reason. I try to use the latest NLog refresh NLog-1.0-Refresh-setup.exe<http://nlog.codeplex.com/releases/32601/download/82217> but first I installed the Nightly Build 2010.06.05.001<http://nlog.codeplex.com/releases/view/46599>and got going, than switched back and set the references to 1.0 refresh and the NLog dlls are netfx2.0 (checked) but my Solution and projects are 3.5 VS2k8. (as ver2 doesn't have NLogC.dll and such) Please what could be the problem? Or how to properly setup and use the C/C++ NLog logging part? Thank you very much Jaroslav |
From: Ron G. <ron...@ya...> - 2010-05-28 19:51:11
|
I'd add in a basic sessionid layout renderer to the console output to make sure you're seeing the expected values: http://nlog-project.org/lr.aspnet-sessionid.html then play around with adding a file target: http://nlog-project.org/target.File.html and something like this: <target name="file" xsi:type="File" fileName="${aspnet-sessionid}.log"/> ________________________________ From: Carlo Lucadei <car...@gm...> To: nlo...@li... Sent: Fri, May 28, 2010 6:23:38 AM Subject: Re: [Nlog-list] IoC with CastleWindsor. Load NLog from config file Hi Ron! 2010/5/28 Ron Grabowski <ron...@ya...> > >There's already an integration assembly that's part of Castle: > >http://github.com/castleproject/Castle.Core/blob/master/src/Castle.Services.Logging.NLogIntegration/NLogLogger.cs >> >[cut] > I try it. It's seems to works fine (below you can find a snippet configuration) but I have a question. If I want to save my log, based on a particular sessionId (i.e: ../../$(logger).log -> sessionId = 12346789 -> 12346789.log) and I dont know its value before because it comes from outside, what can I do? These are the "newest" config files <?xml version="1.0" encoding="utf-8" ?> <configuration> <configSections> <section name="castle" type="Castle.Windsor.Configuration.AppDomain.CastleSectionHandler, Castle.Windsor" /> </configSections> <castle> <facilities> <facility id="logging" type="Castle.Facilities.Logging.LoggingFacility, Castle.Facilities.Logging" loggingApi="nlog" configFile="nlog.config" /> </facilities> <components> ... </components> </castle> </configuration> <!-- This is the nlog.config --> <?xml version="1.0" encoding="utf-8" ?> <configuration> <configSections> <section name="nlog" type="NLog.Config.ConfigSectionHandler, NLog"/> </configSections> <nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <targets> <target name="debugconsole" xsi:type="ColoredConsole" layout="${date:format=HH\:mm\:ss\:fff} ${level} ${message} ${exception:format=Type,Message,StackTrace}" encoding="iso-8859-2"/> </targets> <rules> <logger name="*" minlevel="Debug" writeTo="debugconsole" /> </rules> </nlog> </configuration> Best regards,Carlo |
From: Carlo L. <car...@gm...> - 2010-05-28 10:23:45
|
Hi Ron! 2010/5/28 Ron Grabowski <ron...@ya...> > There's already an integration assembly that's part of Castle: > > > http://github.com/castleproject/Castle.Core/blob/master/src/Castle.Services.Logging.NLogIntegration/NLogLogger.cs > [cut] > I try it. It's seems to works fine (below you can find a snippet configuration) but I have a question. If I want to save my log, based on a particular sessionId (i.e: ../../$(logger).log -> sessionId = 12346789 -> 12346789.log) and I dont know its value before because it comes from outside, what can I do? These are the "newest" config files <?xml version="1.0" encoding="utf-8" ?> <configuration> <configSections> <section name="castle" type="Castle.Windsor.Configuration.AppDomain.CastleSectionHandler, Castle.Windsor" /> </configSections> <castle> <facilities> <facility id="logging" type="Castle.Facilities.Logging.LoggingFacility, Castle.Facilities.Logging" loggingApi="nlog" configFile="nlog.config" /> </facilities> <components> ... </components> </castle> </configuration> <!-- This is the nlog.config --> <?xml version="1.0" encoding="utf-8" ?> <configuration> <configSections> <section name="nlog" type="NLog.Config.ConfigSectionHandler, NLog"/> </configSections> <nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"> <targets> <target name="debugconsole" xsi:type="ColoredConsole" layout="${date:format=HH\:mm\:ss\:fff} ${level} ${message} ${exception:format=Type,Message,StackTrace}" encoding="iso-8859-2"/> </targets> <rules> <logger name="*" minlevel="Debug" writeTo="debugconsole" /> </rules> </nlog> </configuration> Best regards, Carlo |
From: Ron G. <ron...@ya...> - 2010-05-27 22:17:05
|
There's already an integration assembly that's part of Castle: http://github.com/castleproject/Castle.Core/blob/master/src/Castle.Services.Logging.NLogIntegration/NLogLogger.cs Once you have the integration assembly in your bin directory you can follow the instructions on this page to activate it: http://www.castleproject.org/container/facilities/v1rc3/logging/index.html ________________________________ From: Carlo Lucadei <car...@gm...> To: nlo...@li... Sent: Thu, May 27, 2010 11:50:57 AM Subject: [Nlog-list] IoC with CastleWindsor. Load NLog from config file Hi All, I'm using NLog on IoC scenario (I'm using CastleWindsor). I found a way to load NLog from app.config. I defined the nlog section and target as I usually do: <section name="nlog" type="NLog.Config.ConfigSectionHandler, NLog"/> [...] <nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <targets> <target name="debugconsole" xsi:type="ColoredConsole" [...]/> </targets> <rules> <logger name="*" minlevel="Debug" writeTo="debugconsole" /> </rules> </nlog> Then I create the CastleWindsor logger component: <component id="NlogLogger" service="IoC.ILogger, IoC" type="IoC.NLogLogger, IoC" lifestyle="Singleton"> </component> where NlogLogger is a simple wrapper for NLog: public class NLogLogger : ILogger { private NLog.Logger log; public NLogLogger() { log = NLog.LogManager.GetLogger("*"); } #region ILogger Members public void LogDebug(string message) { log.Debug(message); } public bool IsDebugEnabled { get { return log.IsDebugEnabled; } } [...] #endregion } I need to create this wrapper because NLog.Logger doesn't implement an ILogger Interface, otherwise I should be able to load directly NLog.Logger from config file like this: [...] <component id="NlogLogger" service="NLog.ILogger, NLog" type="NLog.Logger, NLoc" lifestyle="Singleton"> </component> It's right? Why NLog.Logger doesn't implement an interface? Best regards, Carlo |
From: Carlo L. <car...@gm...> - 2010-05-27 15:51:09
|
Hi All, I'm using NLog on IoC scenario (I'm using CastleWindsor). I found a way to load NLog from app.config. I defined the nlog section and target as I usually do: <section name="nlog" type="NLog.Config.ConfigSectionHandler, NLog"/> [...] <nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"> <targets> <target name="debugconsole" xsi:type="ColoredConsole" [...]/> </targets> <rules> <logger name="*" minlevel="Debug" writeTo="debugconsole" /> </rules> </nlog> Then I create the CastleWindsor logger component: <component id="NlogLogger" service="IoC.ILogger, IoC" type="IoC.NLogLogger, IoC" lifestyle="Singleton"> </component> where NlogLogger is a simple wrapper for NLog: public class NLogLogger : ILogger { private NLog.Logger log; public NLogLogger() { log = NLog.LogManager.GetLogger("*"); } #region ILogger Members public void LogDebug(string message) { log.Debug(message); } public bool IsDebugEnabled { get { return log.IsDebugEnabled; } } [...] #endregion } I need to create this wrapper because NLog.Logger doesn't implement an ILogger Interface, otherwise I should be able to load directly NLog.Logger from config file like this: [...] <component id="NlogLogger" service="NLog.ILogger, NLog" type="NLog.Logger, NLoc" lifestyle="Singleton"> </component> It's right? Why NLog.Logger doesn't implement an interface? Best regards, Carlo |
From: Jarek K. <ja...@jk...> - 2010-05-24 20:02:03
|
Read more: http://nlog-project.org/2010/05/22/nlog-nightly-builds-available.html Jarek |
From: Andrew S. <ma...@an...> - 2010-05-02 13:03:42
|
Jarek, your WiX installer ran without issue on my x64 win7 machine. Having worked with WiX myself I understand the pain. thanks for putting in the time. - Cheers. On 2 May 2010 15:03, Jarek Kowalski <ja...@jk...> wrote: > Please download and give it a try. Since this is my first WIX project, I'm > interested in getting thorough test coverage from as many platforms as > possible. > > http://bit.ly/9gjhQL > > Thanks, > > Jarek > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Nlog-list mailing list > Nlo...@li... > https://lists.sourceforge.net/lists/listinfo/nlog-list > > -- Kind regards, ---------------------------------------- Andrew Stone Microsoft .NET Consultant AndrewStone.net ma...@an... http://www.andrewstone.net +61 (0)412 488 251 ---------------------------------------- |
From: Jarek K. <ja...@jk...> - 2010-05-02 06:11:07
|
Please download and give it a try. Since this is my first WIX project, I'm interested in getting thorough test coverage from as many platforms as possible. http://bit.ly/9gjhQL Thanks, Jarek |
From: Jarek K. <ja...@jk...> - 2010-04-16 05:38:27
|
Please go to: http://nlog-project.org/mailinglists.html for instructions on joining the mailing list. ----- http://feeds.feedburner.com/~r/nlog/~6/2 http://feeds.feedburner.com/nlog.2.gif -- View this message in context: http://n2.nabble.com/Mailing-List-tp4911437p4911468.html Sent from the NLog-list mailing list archive at Nabble.com. |
From: Nick Z. <nic...@pe...> - 2010-04-16 05:00:00
|
Hi, I would like to join this mailing list. Cheers, Nick Zervoudakis Developer PelicanCorp Software and Services for the Protection of Essential Infrastructure (a) 79 Rokeby Street, Collingwood 3066, VIC, AU (e) nic...@pe... (p) +613 8413 5200 (f) +613 8413 5299 (w) www.pelicancorp.com The information contained in this email communication may be confidential. You should only read, disclose, re-transmit, copy, distribute, act in reliance on or commercialise the information if you are authorised to do so. If you are not the intended recipient of this email communication, please notify us immediately by email at <blocked::mailto:con...@pe...> con...@pe... or reply by email directly to the sender and then destroy any electronic or paper copy of this message. |
From: Jarek K. <ja...@jk...> - 2010-03-30 06:37:04
|
From: http://nlog-project.org/blog/2010/03/29/nlog-wiki-launched.html NLog has a new wiki site available at http://wiki.nlog-project.org/. The goal is to build a repository of user-driven content around NLog including: - FAQs - Tutorials/HOWTOs - Configuration file examples/code snippets - List of references (commercial and open-source projects using NLog) - List of tools and extensions supporting NLog I’ve migrated some (still very little) content from the main site to the wiki, more is on the way, but in order for this effort to be successful, I need lots of help from the NLog community. Please help grow the Wiki by adding new articles and expanding existing ones. One of the areas I would really appreciate your help most is building the list of references on Who_is_using_NLog<http://wiki.nlog-project.org/Who_is_using_NLog>page. A number of commercial and and open source projects are using NLog today, but there is no single place to find those references. If you are using NLog in a project and would like to tell the world about it, please add this information about your project or product to the wiki (make sure to get permission to use your company name and logo first). NLog Wiki is accessible to everyone, registration is very simple and there is no moderation yet – please help it stay like that. All wiki content is licensed under Creative Commons Attribution 3.0 license<http://creativecommons.org/licenses/by/3.0/>. The site is powered by MediaWiki <http://www.mediawiki.org/>. |
From: Jarek K. <ja...@jk...> - 2010-03-13 08:42:42
|
I've just released first preview build of NLog 2.0 on CodePlex. Testing help is greatly appreciated. More information can be found here: http://nlog-project.org/blog/2010/03/12/first-preview-build-of-nlog-2-0-is-available.html |
From: Jarek K. <ja...@jk...> - 2010-02-21 05:29:50
|
FYI: I've just published new blog post on NLog: http://nlog-project.org/blog/2010/02/20/important-nlog-2-0-milestone-reached.html |