https://zbrad.github.io/tags/nlog/Recent content in Nlog on ZBrad's BlogHugoen-usMon, 19 Oct 2015 00:00:00 -0700https://zbrad.github.io/tools/NLogEtw/Mon, 19 Oct 2015 00:00:00 -0700https://zbrad.github.io/tools/NLogEtw/<p>Describes the creation of a new <a href="https://github.com/NLog/NLog/wiki/Extending%20NLog">custom NLog target</a> that provides an <a href="https://msdn.microsoft.com/en-us/library/ms751538(v=vs.110).aspx">ETW source</a> (Event Tracing for Windows) for event processing in Microsoft platforms. This is useful for applications built on NLog, that also need to execute in ETW environments. The code is available on <a href="https://github.com/zbrad/nlogetw">GitHub</a> and the package is available from <a href="https://www.nuget.org/packages/ZBrad.NLogEtw/1.0.0-beta">NuGet</a>.</p> <h2 id="background">Background</h2> <p>I prefer to use NLog within my applications. Recently I&rsquo;ve been creating microservice applications for some customer guidance using the new <a href="https://azure.microsoft.com/en-us/campaigns/service-fabric/">Azure Service Fabric</a>. The issue is that by default, the Visual Studio templates and the debugging environment, use ETW events for diagnostic and logging information. During a debug session it shows a display like:</p>