http://bcl.codeplex.com/releasesbcl Releases Rss Descriptionhttp://bcl.codeplex.com/releases/view/99984<div class="wikidoc">The TraceEvent.bin.zip contains the TraceEvent.dll as well as it PDB and XML documentation. It also contains the unmananged DLLs for the X86 architecture (AMD64 available in the src distribution). See the README.txt for more details. <br /><br />The TraceEvent.src.zip can simply be copied locally and built using the .SLN file <br />If you unpack the PerfMonitor 2.0 release source beside it, you can build PerfMonitor as a sample. <br /><br />Version 1.2.7. Numerous changes (over a year&#39;s worth). There are a few breaking changes, but the port should be easy. <br /><br />TraceEvent supports stacks and symbol lookup for stacks, including using Symbol servers. It also supports the &#39;RegisterTraceEventParser&#39; that knows how to decode any ETW provider registered officially with the Operating system (that is all the OS supplied ETW providers). <br /><br />TraceEvent also supports System.Diagnostics.Tracing.EventSources, and in particular knows how to take an EventSource name and create GUID from it the way an eventSource does (see GetEventSourceGuidFromName). <br /><br />Depending on the exact functionality you use in TraceEvent you MIGHT need additional unmanaged DLLs. This Bin release above has the X86 version of this, however the source code has the DLLs for either. See the README.txt in the binary drop (or in the supportsFiles directory) for details on when the unmanaged DLLs are used (mostly for symbol lookup)</div><div class="ClearBoth"></div>VanceMorrisonWed, 09 Jan 2013 15:57:27 GMTUpdated Release: TraceEvent 1.2.7.1 (Jan 09, 2013) 20130109035727Phttp://bcl.codeplex.com/releases/view/99984 <div class="wikidoc">The TraceEvent.bin.zip contains the TraceEvent.dll as well as it PDB and XML documentation. It also contains the unmananged DLLs for the X86 architecture (AMD64 available in the src distribution). See the README.txt for more details. <br> <br> The TraceEvent.src.zip can simply be copied locally and built using the .SLN file <br> If you unpack the PerfMonitor 2.0 release source beside it, you can build PerfMonitor as a sample. <br> <br> Version 1.2.7. Numerous changes (over a year&#39;s worth). There are a few breaking changes, but the port should be easy. <br> <br> TraceEvent supports stacks and symbol lookup for stacks, including using Symbol servers. It also supports the &#39;RegisterTraceEventParser&#39; that knows how to decode any ETW provider registered officially with the Operating system (that is all the OS supplied ETW providers). <br> <br> TraceEvent also supports System.Diagnostics.Tracing.EventSources, and in particular knows how to take an EventSource name and create GUID from it the way an eventSource does (see GetEventSourceGuidFromName). <br> <br> Depending on the exact functionality you use in TraceEvent you MIGHT need additional unmanaged DLLs. This Bin release above has the X86 version of this, however the source code has the DLLs for either. See the README.txt in the binary drop (or in the supportsFiles directory) for details on when the unmanaged DLLs are used (mostly for symbol lookup)</div> <div></div> Wed, 09 Jan 2013 15:57:27 GMTReleased: TraceEvent 1.2.7.1 (Jan 09, 2013) 20130109035727Phttp://bcl.codeplex.com/releases/view/99985<div class="wikidoc">To use the binary, simply open the PerfMonitor.bin.zip link above and drag the contents to your machine. Simply run it from the command line without arguments for help getting started. <br /><br />The source code should be unpacked into a directory BESIDE the TraceEvent 1.2.7 downloadfor the solution to build. <br /><br />PerfMonitor was mostly just updated to track changes in TraceEvent and to harmonize with PerfView (I tried to make the command parameters the same when possible, and to act like a &#39;command line&#39; version of PerfView)_. In particular it supports ETL.ZIP files. The recommendation, however is to use PerfView (bing it for download site). PerfMonitor is really just an &#39;exposed source;&#39; version of PerfVIew that demos TraceEvent.<br /><br />This new PerfMonitor uses the same &#39;SupportFiles&#39; class that allows PerfMonitor to be a single EXE event though it needs various support DLLs internally (like TraceEvent, msdia100.dll ...). See SupportFiles in the source code for more. This is pretty useful for any code.</div><div class="ClearBoth"></div>VanceMorrisonWed, 09 Jan 2013 15:53:06 GMTUpdated Release: PerfMonitor 2.01 (Jan 09, 2013) 20130109035306Phttp://bcl.codeplex.com/releases/view/99985 <div class="wikidoc">To use the binary, simply open the PerfMonitor.bin.zip link above and drag the contents to your machine. Simply run it from the command line without arguments for help getting started. <br> <br> The source code should be unpacked into a directory BESIDE the TraceEvent 1.2.7 downloadfor the solution to build. <br> <br> PerfMonitor was mostly just updated to track changes in TraceEvent and to harmonize with PerfView (I tried to make the command parameters the same when possible, and to act like a &#39;command line&#39; version of PerfView)_. In particular it supports ETL.ZIP files. The recommendation, however is to use PerfView (bing it for download site). PerfMonitor is really just an &#39;exposed source;&#39; version of PerfVIew that demos TraceEvent.<br> <br> This new PerfMonitor uses the same &#39;SupportFiles&#39; class that allows PerfMonitor to be a single EXE event though it needs various support DLLs internally (like TraceEvent, msdia100.dll ...). See SupportFiles in the source code for more. This is pretty useful for any code.</div> <div></div> Wed, 09 Jan 2013 15:53:06 GMTReleased: PerfMonitor 2.01 (Jan 09, 2013) 20130109035306Phttp://bcl.codeplex.com/releases/view/99984<div class="wikidoc">The TraceEvent.bin.zip contains the TraceEvent.dll as well as it PDB and XML documentation. It also contains the unmananged DLLs for the X86 architecture (AMD64 available in the src distribution). See the README.txt for more details. <br /><br />The TraceEvent.src.zip can simply be copied locally and built using the .SLN file <br />If you unpack the PerfMonitor 2.0 release source beside it, you can build PerfMonitor as a sample. <br /><br />Version 1.2.7. Numerous changes (over a year&#39;s worth). There are a few breaking changes, but the port should be easy. <br /><br />TraceEvent supports stacks and symbol lookup for stacks, including using Symbol servers. It also supports the &#39;RegisterTraceEventParser&#39; that knows how to decode any ETW provider registered officially with the Operating system (that is all the OS supplied ETW providers). <br /><br />TraceEvent also supports System.Diagnostics.Tracing.EventSources, and in particular knows how to take an EventSource name and create GUID from it the way an eventSource does (see GetEventSourceGuidFromName). <br /><br />Depending on the exact functionality you use in TraceEvent you MIGHT need additional unmanaged DLLs. This Bin release above has the X86 version of this, however the source code has the DLLs for either. See the README.txt in the binary drop (or in the supportsFiles directory) for details on when the unmanaged DLLs are used (mostly for symbol lookup)</div><div class="ClearBoth"></div>VanceMorrisonWed, 09 Jan 2013 15:52:49 GMTUpdated Release: TraceEvent 1.2.7.1 (Jan 09, 2013) 20130109035249Phttp://bcl.codeplex.com/releases/view/99984<div class="wikidoc">The TraceEvent.bin.zip contains the TraceEvent.dll as well as it PDB and XML documentation. It also contains the unmananged DLLs for the X86 architecture (AMD64 available in the src distribution). See the README.txt for more details. <br /><br />The TraceEvent.src.zip can simply be copied locally and built using the .SLN file <br />If you unpack the PerfMonitor 2.0 release source beside it, you can build PerfMonitor as a sample. <br /><br />Version 1.2.7. Numerous changes (over a year&#39;s worth). There are a few breaking changes, but the port should be easy. <br /><br />TraceEvent supports stacks and symbol lookup for stacks, including using Symbol servers. It also supports the &#39;RegisterTraceEventParser&#39; that knows how to decode any ETW provider registered officially with the Operating system (that is all the OS supplied ETW providers). <br /><br />TraceEvent also supports System.Diagnostics.Tracing.EventSources, and in particular knows how to take an EventSource name and create GUID from it the way an eventSource does (see GetEventSourceGuidFromName). <br /><br />Depending on the exact functionality you use in TraceEvent you MIGHT need additional unmanaged DLLs. This Bin release above has the X86 version of this, however the source code has the DLLs for either. See the README.txt in the binary drop (or in the supportsFiles directory) for details on when the unmanaged DLLs are used (mostly for symbol lookup)</div><div class="ClearBoth"></div>VanceMorrisonWed, 09 Jan 2013 15:52:32 GMTUpdated Release: TraceEvent 1.2.7.1 (Jan 06, 2013) 20130109035232Phttp://bcl.codeplex.com/releases/view/99985<div class="wikidoc">To use the binary, simply open the PerfMonitor.bin.zip link above and drag the contents to your machine. Simply run it from the command line without arguments for help getting started. <br /><br />The source code should be unpacked into a directory BESIDE the TraceEvent 1.2.7 downloadfor the solution to build. <br /><br />PerfMonitor was mostly just updated to track changes in TraceEvent and to harmonize with PerfView (I tried to make the command parameters the same when possible, and to act like a &#39;command line&#39; version of PerfView)_. In particular it supports ETL.ZIP files. The recommendation, however is to use PerfView (bing it for download site). PerfMonitor is really just an &#39;exposed source;&#39; version of PerfVIew that demos TraceEvent.<br /><br />This new PerfMonitor uses the same &#39;SupportFiles&#39; class that allows PerfMonitor to be a single EXE event though it needs various support DLLs internally (like TraceEvent, msdia100.dll ...). See SupportFiles in the source code for more. This is pretty useful for any code.</div><div class="ClearBoth"></div>VanceMorrisonWed, 09 Jan 2013 15:50:26 GMTUpdated Release: PerfMonitor 2.01 (Jan 06, 2013) 20130109035026Phttp://bcl.codeplex.com/releases/view/99984<div class="wikidoc">The TraceEvent.bin.zip contains the TraceEvent.dll as well as it PDB and XML documentation. It also contains the unmananged DLLs for the X86 architecture (AMD64 available in the src distribution). See the README.txt for more details. <br /><br />The TraceEvent.src.zip can simply be copied locally and built using the .SLN file <br />If you unpack the PerfMonitor 2.0 release source beside it, you can build PerfMonitor as a sample. <br /><br />Version 1.2.7. Numerous changes (over a year&#39;s worth). There are a few breaking changes, but the port should be easy. <br /><br />TraceEvent supports stacks and symbol lookup for stacks, including using Symbol servers. It also supports the &#39;RegisterTraceEventParser&#39; that knows how to decode any ETW provider registered officially with the Operating system (that is all the OS supplied ETW providers). <br /><br />TraceEvent also supports System.Diagnostics.Tracing.EventSources, and in particular knows how to take an EventSource name and create GUID from it the way an eventSource does (see GetEventSourceGuidFromName). <br /><br />Depending on the exact functionality you use in TraceEvent you MIGHT need additional unmanaged DLLs. This Bin release above has the X86 version of this, however the source code has the DLLs for either. See the README.txt in the binary drop (or in the supportsFiles directory) for details on when the unmanaged DLLs are used (mostly for symbol lookup)</div><div class="ClearBoth"></div>VanceMorrisonWed, 09 Jan 2013 13:20:30 GMTUpdated Release: TraceEvent 1.2.7 (Jan 06, 2013) 20130109012030Phttp://bcl.codeplex.com/releases/view/99984 <div class="wikidoc">The TraceEvent.bin.zip contains the TraceEvent.dll as well as it PDB and XML documentation. It also contains the unmananged DLLs for the X86 architecture (AMD64 available in the src distribution). See the README.txt for more details. <br> <br> The TraceEvent.src.zip can simply be copied locally and built using the .SLN file <br> If you unpack the PerfMonitor 2.0 release source beside it, you can build PerfMonitor as a sample. <br> <br> Version 1.2.7. Numerous changes (over a year&#39;s worth). There are a few breaking changes, but the port should be easy. <br> <br> TraceEvent supports stacks and symbol lookup for stacks, including using Symbol servers. It also supports the &#39;RegisterTraceEventParser&#39; that knows how to decode any ETW provider registered officially with the Operating system (that is all the OS supplied ETW providers). <br> <br> TraceEvent also supports System.Diagnostics.Tracing.EventSources, and in particular knows how to take an EventSource name and create GUID from it the way an eventSource does (see GetEventSourceGuidFromName). <br> <br> Depending on the exact functionality you use in TraceEvent you MIGHT need additional unmanaged DLLs. This Bin release above has the X86 version of this, however the source code has the DLLs for either. See the README.txt in the binary drop (or in the supportsFiles directory) for details on when the unmanaged DLLs are used (mostly for symbol lookup)</div> <div></div> Wed, 09 Jan 2013 13:20:30 GMTReleased: TraceEvent 1.2.7 (Jan 06, 2013) 20130109012030Phttp://bcl.codeplex.com/releases/view/99985<div class="wikidoc">To use the binary, simply open the PerfMonitor.bin.zip link above and drag the contents to your machine. Simply run it from the command line without arguments for help getting started. <br /><br />The source code should be unpacked into a directory BESIDE the TraceEvent 1.2.7 downloadfor the solution to build. <br /><br />PerfMonitor was mostly just updated to track changes in TraceEvent and to harmonize with PerfView (I tried to make the command parameters the same when possible, and to act like a &#39;command line&#39; version of PerfView)_. In particular it supports ETL.ZIP files. The recommendation, however is to use PerfView (bing it for download site). PerfMonitor is really just an &#39;exposed source;&#39; version of PerfVIew that demos TraceEvent.<br /><br />This new PerfMonitor uses the same &#39;SupportFiles&#39; class that allows PerfMonitor to be a single EXE event though it needs various support DLLs internally (like TraceEvent, msdia100.dll ...). See SupportFiles in the source code for more. This is pretty useful for any code.</div><div class="ClearBoth"></div>VanceMorrisonWed, 09 Jan 2013 13:17:28 GMTUpdated Release: PerfMonitor 2.0 (Jan 06, 2013) 20130109011728Phttp://bcl.codeplex.com/releases/view/99985 <div class="wikidoc">To use the binary, simply open the PerfMonitor.bin.zip link above and drag the contents to your machine. Simply run it from the command line without arguments for help getting started. <br> <br> The source code should be unpacked into a directory BESIDE the TraceEvent 1.2.7 downloadfor the solution to build. <br> <br> PerfMonitor was mostly just updated to track changes in TraceEvent and to harmonize with PerfView (I tried to make the command parameters the same when possible, and to act like a &#39;command line&#39; version of PerfView)_. In particular it supports ETL.ZIP files. The recommendation, however is to use PerfView (bing it for download site). PerfMonitor is really just an &#39;exposed source;&#39; version of PerfVIew that demos TraceEvent.<br> <br> This new PerfMonitor uses the same &#39;SupportFiles&#39; class that allows PerfMonitor to be a single EXE event though it needs various support DLLs internally (like TraceEvent, msdia100.dll ...). See SupportFiles in the source code for more. This is pretty useful for any code.</div> <div></div> Wed, 09 Jan 2013 13:17:28 GMTReleased: PerfMonitor 2.0 (Jan 06, 2013) 20130109011728Phttp://bcl.codeplex.com/releases/view/99985<div class="wikidoc">To use the binary, simply open the PerfMonitor.bin.zip link above and drag the contents to your machine. Simply run it from the command line without arguments for help getting started. <br /><br />The source code should be unpacked into a directory BESIDE the TraceEvent 1.2.7 downloadfor the solution to build. <br /><br />PerfMonitor was mostly just updated to track changes in TraceEvent and to harmonize with PerfView (I tried to make the command parameters the same when possible, and to act like a &#39;command line&#39; version of PerfView)_. In particular it supports ETL.ZIP files. The recommendation, however is to use PerfView (bing it for download site). PerfMonitor is really just an &#39;exposed source;&#39; version of PerfVIew that demos TraceEvent.<br /><br />This new PerfMonitor uses the same &#39;SupportFiles&#39; class that allows PerfMonitor to be a single EXE event though it needs various support DLLs internally (like TraceEvent, msdia100.dll ...). See SupportFiles in the source code for more. This is pretty useful for any code.</div><div class="ClearBoth"></div>VanceMorrisonWed, 09 Jan 2013 13:17:07 GMTUpdated Release: PerfMonitor 2.0 (Jan 06, 2013) 20130109011707Phttp://bcl.codeplex.com/releases/view/99984<div class="wikidoc">The TraceEvent.bin.zip contains the TraceEvent.dll as well as it PDB and XML documentation. It also contains the unmananged DLLs for the X86 architecture (AMD64 available in the src distribution). See the README.txt for more details. <br /><br />The TraceEvent.src.zip can simply be copied locally and built using the .SLN file <br />If you unpack the PerfMonitor 2.0 release source beside it, you can build PerfMonitor as a sample. <br /><br />Version 1.2.7. Numerous changes (over a year&#39;s worth). There are a few breaking changes, but the port should be easy. <br /><br />TraceEvent supports stacks and symbol lookup for stacks, including using Symbol servers. It also supports the &#39;RegisterTraceEventParser&#39; that knows how to decode any ETW provider registered officially with the Operating system (that is all the OS supplied ETW providers). <br /><br />TraceEvent also supports System.Diagnostics.Tracing.EventSources, and in particular knows how to take an EventSource name and create GUID from it the way an eventSource does (see GetEventSourceGuidFromName). <br /><br />Depending on the exact functionality you use in TraceEvent you MIGHT need additional unmanaged DLLs. This Bin release above has the X86 version of this, however the source code has the DLLs for either. See the README.txt in the binary drop (or in the supportsFiles directory) for details on when the unmanaged DLLs are used (mostly for symbol lookup)</div><div class="ClearBoth"></div>VanceMorrisonMon, 07 Jan 2013 04:19:30 GMTUpdated Release: TraceEvent 1.2.7 (Jan 06, 2013) 20130107041930Ahttp://bcl.codeplex.com/releases/view/99984 <div class="wikidoc">The TraceEvent.bin.zip contains the TraceEvent.dll as well as it PDB and XML documentation. It also contains the unmananged DLLs for the X86 architecture (AMD64 available in the src distribution). See the README.txt for more details. <br> <br> The TraceEvent.src.zip can simply be copied locally and built using the .SLN file <br> If you unpack the PerfMonitor 2.0 release source beside it, you can build PerfMonitor as a sample. <br> <br> Version 1.2.7. Numerous changes (over a year&#39;s worth). There are a few breaking changes, but the port should be easy. <br> <br> TraceEvent supports stacks and symbol lookup for stacks, including using Symbol servers. It also supports the &#39;RegisterTraceEventParser&#39; that knows how to decode any ETW provider registered officially with the Operating system (that is all the OS supplied ETW providers). <br> <br> TraceEvent also supports System.Diagnostics.Tracing.EventSources, and in particular knows how to take an EventSource name and create GUID from it the way an eventSource does (see GetEventSourceGuidFromName). <br> <br> Depending on the exact functionality you use in TraceEvent you MIGHT need additional unmanaged DLLs. This Bin release above has the X86 version of this, however the source code has the DLLs for either. See the README.txt in the binary drop (or in the supportsFiles directory) for details on when the unmanaged DLLs are used (mostly for symbol lookup)</div> <div></div> Mon, 07 Jan 2013 04:19:30 GMTReleased: TraceEvent 1.2.7 (Jan 06, 2013) 20130107041930Ahttp://bcl.codeplex.com/releases/view/99985<div class="wikidoc">To use the binary, simply open the PerfMonitor.bin.zip link above and drag the contents to your machine. Simply run it from the command line without arguments for help getting started. <br /><br />The source code should be unpacked into a directory BESIDE the TraceEvent 1.2.7 downloadfor the solution to build. <br /><br />PerfMonitor was mostly just updated to track changes in TraceEvent and to harmonize with PerfView (I tried to make the command parameters the same when possible, and to act like a &#39;command line&#39; version of PerfView)_. In particular it supports ETL.ZIP files. The recommendation, however is to use PerfView (bing it for download site). PerfMonitor is really just an &#39;exposed source;&#39; version of PerfVIew that demos TraceEvent.<br /><br />This new PerfMonitor uses the same &#39;SupportFiles&#39; class that allows PerfMonitor to be a single EXE event though it needs various support DLLs internally (like TraceEvent, msdia100.dll ...). See SupportFiles in the source code for more. This is pretty useful for any code.</div><div class="ClearBoth"></div>VanceMorrisonMon, 07 Jan 2013 04:15:19 GMTUpdated Release: PerfMonitor 2.0 (Jan 06, 2013) 20130107041519Ahttp://bcl.codeplex.com/releases/view/99985 <div class="wikidoc">To use the binary, simply open the PerfMonitor.bin.zip link above and drag the contents to your machine. Simply run it from the command line without arguments for help getting started. <br> <br> The source code should be unpacked into a directory BESIDE the TraceEvent 1.2.7 downloadfor the solution to build. <br> <br> PerfMonitor was mostly just updated to track changes in TraceEvent and to harmonize with PerfView (I tried to make the command parameters the same when possible, and to act like a &#39;command line&#39; version of PerfView)_. In particular it supports ETL.ZIP files. The recommendation, however is to use PerfView (bing it for download site). PerfMonitor is really just an &#39;exposed source;&#39; version of PerfVIew that demos TraceEvent.<br> <br> This new PerfMonitor uses the same &#39;SupportFiles&#39; class that allows PerfMonitor to be a single EXE event though it needs various support DLLs internally (like TraceEvent, msdia100.dll ...). See SupportFiles in the source code for more. This is pretty useful for any code.</div> <div></div> Mon, 07 Jan 2013 04:15:19 GMTReleased: PerfMonitor 2.0 (Jan 06, 2013) 20130107041519Ahttp://bcl.codeplex.com/releases/view/99985<div class="wikidoc">PerfMonitor was mostly just updated to track changes in TraceEvent and to harmonize with PerfView (I tried to make the command parameters the same when possible, and to act like a &#39;command line&#39; version of PerfView)_. In particular it supports ETL.ZIP files. The recommendation, however is to use PerfView (bing it for download site). PerfMonitor is really just an &#39;exposed source;&#39; version of PerfVIew that demos TraceEvent.<br /><br />This new PerfMonitor uses the same &#39;SupportFiles&#39; class that allows PerfMonitor to be a single EXE event though it needs various support DLLs internally (like TraceEvent, msdia100.dll ...). See SupportFiles in the source code for more. This is pretty useful for any code.</div><div class="ClearBoth"></div>VanceMorrisonMon, 07 Jan 2013 04:12:40 GMTUpdated Release: PerfMonitor 2.0 (Jan 06, 2013) 20130107041240Ahttp://bcl.codeplex.com/releases/view/99985<div class="wikidoc">PerfMonitor was mostly just updated to track changes in TraceEvent and to harmonize with PerfView (I tried to make the command parameters the same when possible, and to act like a &#39;command line&#39; version of PerfView)_. In particular it supports ETL.ZIP files. The recommendation, however is to use PerfView (bing it for download site). PerfMonitor is really just an &#39;exposed source;&#39; version of PerfVIew that demos TraceEvent.<br /><br />This new PerfMonitor uses the same &#39;SupportFiles&#39; class that allows PerfMonitor to be a single EXE event though it needs various support DLLs internally (like TraceEvent, msdia100.dll ...). See SupportFiles in the source code for more. This is pretty useful for any code.</div><div class="ClearBoth"></div>VanceMorrisonMon, 07 Jan 2013 04:01:00 GMTUpdated Release: PerfMonitor 2.0 (Jan 06, 2013) 20130107040100Ahttp://bcl.codeplex.com/releases/view/99985 <div class="wikidoc">PerfMonitor was mostly just updated to track changes in TraceEvent and to harmonize with PerfView (I tried to make the command parameters the same when possible, and to act like a &#39;command line&#39; version of PerfView)_. In particular it supports ETL.ZIP files. The recommendation, however is to use PerfView (bing it for download site). PerfMonitor is really just an &#39;exposed source;&#39; version of PerfVIew that demos TraceEvent.<br> <br> This new PerfMonitor uses the same &#39;SupportFiles&#39; class that allows PerfMonitor to be a single EXE event though it needs various support DLLs internally (like TraceEvent, msdia100.dll ...). See SupportFiles in the source code for more. This is pretty useful for any code.</div> <div></div> Mon, 07 Jan 2013 04:01:00 GMTReleased: PerfMonitor 2.0 (Jan 06, 2013) 20130107040100Ahttp://bcl.codeplex.com/releases/view/99985<div class="wikidoc">PerfMonitor was mostly just updated to track changes in TraceEvent and to harmonize with PerfView (I tried to make the command parameters the same when possible, and to act like a &#39;command line&#39; version of PerfView)_. In particular it supports ETL.ZIP files. The recommendation, however is to use PerfView (bing it for download site). PerfMonitor is really just an &#39;exposed source;&#39; version of PerfVIew that demos TraceEvent.<br /><br />This new PerfMonitor uses the same &#39;SupportFiles&#39; class that allows PerfMonitor to be a single EXE event though it needs various support DLLs internally (like TraceEvent, msdia100.dll ...). See SupportFiles in the source code for more. This is pretty useful for any code.</div><div class="ClearBoth"></div>VanceMorrisonMon, 07 Jan 2013 04:00:41 GMTUpdated Release: PerfMonitor Version 2.0 (Jan 06, 2013) 20130107040041A