Introduction Tutorial: Logging ETW events in C#: System.Diagnostics.Tracing.EventSource

re: Introduction Tutorial: Logging ETW events in C#: System.Diagnostics.Tracing.EventSource

asava samuel — Fri, 12 Apr 2013 19:27:48 GMT

This logger works really well:

www.kellermansoftware.com/p-14-net-logging-library.aspx

re: Introduction Tutorial: Logging ETW events in C#: System.Diagnostics.Tracing.EventSource

Twista27 — Thu, 31 Jan 2013 09:39:11 GMT

Thanks for the reminder about creating a manifest. I'm currently building our own TraceEventParser for specific needs.

re: Introduction Tutorial: Logging ETW events in C#: System.Diagnostics.Tracing.EventSource

Vance Morrison — Wed, 30 Jan 2013 17:12:45 GMT

A future version of WPA will simply 'fix this' as they will read the manifest that the EventSource emits. We have an internal tool that I will blog about in the several weeks that will take an eventSource and publish its manifest in a way that windows tools including WPA. In the mean time you have to either use PerfView as to view as a work-around, or build and register the EventSource manifest (I am not going to bother to explain how to do this, either you are motivated enough to figure it out, or you will have to wait until I blog about the tool.

re: Introduction Tutorial: Logging ETW events in C#: System.Diagnostics.Tracing.EventSource

Twista27 — Wed, 30 Jan 2013 15:15:32 GMT

How can I create the required views and profiles for the Windows Performance Analyzer for my custom event source. Although I do see events on the graph, I don't see any of their names.

re: Introduction Tutorial: Logging ETW events in C#: System.Diagnostics.Tracing.EventSource

SMurray — Mon, 28 Jan 2013 21:27:08 GMT

Found a bug in the implementation:

Per MSDN, the EventTraceProperties.LoggerNameBuffer needs to come before EventTraceProperties.LogFileNameBuffer in NativeMethods.cs

Fixing this also needs an update of the constructor so that the LogFileNameOffset and LoggerNameOffset are intialized correctly.

re: Introduction Tutorial: Logging ETW events in C#: System.Diagnostics.Tracing.EventSource

Vance Morrison — Fri, 25 Jan 2013 21:30:51 GMT

Channel support is not official and is was not a priority for the sample.

re: Introduction Tutorial: Logging ETW events in C#: System.Diagnostics.Tracing.EventSource

SGarratt — Fri, 25 Jan 2013 20:38:03 GMT

What happened to the ChannelAttribute from the sample?

re: Introduction Tutorial: Logging ETW events in C#: System.Diagnostics.Tracing.EventSource

Andre.Ziegler — Sun, 23 Sep 2012 15:10:40 GMT

ah, ok. I only saw some ETW code in the BCL repository and thought this is the code.

But an you still provide a NuGet package for VS2010/.net 4.0 users to use the EventSource easily?

re: Introduction Tutorial: Logging ETW events in C#: System.Diagnostics.Tracing.EventSource

Vance Morrison — Fri, 21 Sep 2012 15:00:39 GMT

EventSource is not on codeplex, but the version that i posted on this bog is almost identical to the V4.5 version. That is the intent of that code (to allow you to easily transition to the offiical version.

As to the whether it is better to put code in the framework or simply distribute it as a library, that is a trickier question. The general answer is that 'core' infrastructure that does not change much is useful to have in a framework. Code that is pretty specialized (not used by most apps) and/or evolving rapidly benefits from the 'ship as a library' approach. Both techniques have their merits.

re: Introduction Tutorial: Logging ETW events in C#: System.Diagnostics.Tracing.EventSource

Andre.Ziegler — Tue, 04 Sep 2012 21:49:51 GMT

is the EventSource class from codeplex compatible to the version in .net 4.5? Can I use the same code and add switches to use the codeplex version in .net 4.0 and the framework version in .net 4.5?

And why are you doing the opposite of all other teams? They stripe out functionality into NuGet packages to update them faster and you move it to the core framework which makes it harder to get updates (special hotfixes or service packs).