NTrace - High Performance Tracing for .NET Applications

New Post: preprocessor does not handle "Enabled" properties?

jrvjrv — Fri, 01 Mar 2013 13:01:20 GMT

I built a new instrumented windows app and added some tracing on the Form constructor. I was able to get some tracing to work, but the "Enabled" property did not preprocess well. This is the code

if (EtwTrace.Enabled)
{
    // Do something interesting
}

and this is the pre-processed result:

if (EtwTraceInstrumentedWinForms.TraceHelper.provider.Enabled)
{
    // Do something interesting
}

The class name "EtwTrace" has not been cleared. If I fix this up in the original code to

            if (InstrumentedWinForms.TraceHelper.provider.Enabled)

it works, of course, but then the preprocessor is not used.

Similar problems happen with EtwTrace.TraceFlagEnabled and EtwTrace.TraceFlagAndLevelEnabled.

I was using MS Visual Studio 10 SP1, with version 2.0.0.0 of NTrace downloaded in a zip named NTrace.2.0.141.0.zip

Have I missed some important step?

JR VanMechelen

New Post: Support for Channels

SGarratt — Sat, 26 Jan 2013 08:29:58 GMT

Will you be including support for channels in the next version? I understand that these are required to get traces into Event Viewer.

New Post: NTrace support for VS2012

eranahare — Sun, 02 Dec 2012 15:36:00 GMT

Great, thanks!

Do you have any estimation about when you'll have a testable build?

Thanks,

--Eran

New Post: NTrace support for VS2012

ahopper — Thu, 29 Nov 2012 17:50:09 GMT

I welcome any and all beta testers!

And I meant that I'll be *adding* support for 4.5; prior versions should continue to work.

On Nov 29, 2012 10:27 AM, "eranahare" <notifications@codeplex.com> wrote:

From: eranahare

Hi Andy,

Thanks for your reply.

Do you have any ETA for the VS2012 NTrace? I'd like to be a Beta tester:-)

Something I didn't quite understand re/ your last sentence - does it mean that it will work just with 4.5 on 2012, or will it still support earlier .net versions (as 2010 supports 3.5)?

Thanks,

--Eran

Read the full discussion online.

To add a post to this discussion, reply to this email (NTrace@discussions.codeplex.com)

To start a new discussion for this project, email NTrace@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com

New Post: NTrace support for VS2012

eranahare — Thu, 29 Nov 2012 15:27:49 GMT

Hi Andy,

Thanks for your reply.

Do you have any ETA for the VS2012 NTrace? I'd like to be a Beta tester:-)

Something I didn't quite understand re/ your last sentence - does it mean that it will work just with 4.5 on 2012, or will it still support earlier .net versions (as 2010 supports 3.5)?

Thanks,

--Eran

New Post: NTrace support for VS2012

ahopper — Thu, 29 Nov 2012 14:54:29 GMT

Hey, Eran-

I don't check this account as often; sorry it took so long to respond. Yes, I'm porting NTrace to 2012 and the new MSBuild targets for 4.5.

-Andy

On Nov 29, 2012 9:44 AM, "eranahare" <notifications@codeplex.com> wrote:

From: eranahare

Thanks Andre.

This solution will not work for us:

We have a lot of NTrace code in out product and migrating it will require a lot of dev and test work
We currently work with .net 3.5 and don't have any plans moving to a later version in the coming future

I don't know what's the maintenance level of NTrace these days, but I need to get any answer re/ NTrace support for VS2012, so we can plan accordingly.

Thanks,

--Eran

Read the full discussion online.

To add a post to this discussion, reply to this email (NTrace@discussions.codeplex.com)

To start a new discussion for this project, email NTrace@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com

New Post: NTrace support for VS2012

eranahare — Thu, 29 Nov 2012 14:44:45 GMT

Thanks Andre.

This solution will not work for us:

We have a lot of NTrace code in out product and migrating it will require a lot of dev and test work
We currently work with .net 3.5 and don't have any plans moving to a later version in the coming future

I don't know what's the maintenance level of NTrace these days, but I need to get any answer re/ NTrace support for VS2012, so we can plan accordingly.

Thanks,

--Eran

New Post: NTrace support for VS2012

AndreZiegler — Sun, 25 Nov 2012 21:42:41 GMT

.net 4.5 has ETW support build in with the class System.Diagnostics.Tracing.EventSource

http://msdn.microsoft.com/en-us/library/system.diagnostics.tracing.eventsource.aspx

New Post: NTrace support for VS2012

eranhare — Wed, 21 Nov 2012 09:03:51 GMT

Hi,

Are there any plans for VS2012 support? If so, is there any ETA for that?

We're currently heavily using NTrace with VS2010, and about to migrate our source code to VS2012, and from initial tests we saw that NTrace is not supported.

Thanks,

--Eran

Source code checked in, #81799

Project Collection Service Accounts — Mon, 01 Oct 2012 21:57:23 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #81798

Project Collection Service Accounts — Mon, 01 Oct 2012 21:51:05 GMT

Checked in by server upgrade

New Comment on "How to use NTrace"

FredStephens — Thu, 20 Sep 2012 20:40:32 GMT

Also when tweaking an exisiting project the TraceHelper.cs file has to have a build action of Instrument to instantiate the TraceHelper.providor object.

New Comment on "How to use NTrace"

FredStephens — Thu, 20 Sep 2012 19:04:43 GMT

Previous comment applies to Tweak An Existing Project

New Comment on "How to use NTrace"

FredStephens — Thu, 20 Sep 2012 19:01:34 GMT

To get the NTRACE tab to appear under your project properties. You need to another line after <TargetFrameworkversion> to specify that there is a new project type for NTrace and a C# project. <TargetFrameworkVersion>v4.0</TargetFrameworkVersion> <ProjectTypeGuids>{B5E33638-F656-4309-B8B1-11385E5F1346};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids>

New Post: Converting Existing Projects or WinForm project that do not seem to instrumented

FredStephens — Wed, 16 May 2012 22:20:17 GMT

Follow the documentation steps for "Tweak An Existing Project" and while you are editing the project file you need to also change the ItemGroup for compile.

The keyword changes from Compile to Instrument, note you do not instrument a designer file just the base class.

<ItemGroup>
    <Instrument Include="OvDotNetApi.cs">
      <SubType>Component</SubType>
    </Instrument>
    <Compile Include="OvDotNetApi.Designer.cs">
      <DependentUpon>OvDotNetApi.cs</DependentUpon>
    </Compile>
    <Instrument Include="MemoryMappedFile.cs" />
    <Instrument Include="OvInterface.cs">
</ItemGroup>

I have also seen this error when creating a instrumented winform solution.

Created Issue: Null string parameters, causes problems [12158]

FredStephens — Wed, 16 May 2012 22:05:40 GMT

String retVal = null;
EtxTrace.Trace("Search Result = {0}",retVal);

Also if you specific a negative number it compiles on some systems not others.

EtwTrace.Trace("Return Index {0}",-1);

New Post: Status of NTrace?

dvdstelt — Mon, 07 May 2012 12:43:17 GMT

What is the status of this project? Also because the last version is a beta version?!?!

Is it complete and perfect? Or is it just not worked on anymore?

Updated Wiki: Home

ahopper — Wed, 18 Jan 2012 18:33:16 GMT

Project Description
NTrace is a library that provides flexible, high-performance, and zero-config trace logging for your C# applications.
NTrace is currently 100% C#.

(Did you come here looking for Johannes Passing's dynamic function boundary tracing toolkit? If so, click here.)

What is NTrace?

NTrace is a combination of a runtime framework and a code preprocessor that provides an API for using Event Tracing for Windows (ETW) in your managed code. In practice, it's a lot like theWindows Trace Preprocessor (WPP).

Why would I want to use NTrace?

There are two high-level reasons why you'd want to use NTrace. The first is that it allows you to have trace instrumentation that can be enabled and disabled at runtime without having to modify any configuration files. The second is that the tracing capabilities provided by the ETW subsystem are very efficient and flexible. We've tried to preserve as much of the simplicity of using Trace.WriteLine while providing access to all of the features of WPP/ETW. The end result is that you have a great way to troubleshoot your code when it's out in the field.

Requirements

In order to use NTrace, your code needs to meet the following criteria:

You must be using the .NET 2.0 (or later) runtime
You must be using Visual Studio 2008 or Visual Studio 2010
Your code must be C# (VB support still eludes us due to differences in the NRefactory parsers)

Documentation

For more information (including a tutorial for how one can capture and view trace logs using NTrace/ETW) please refer to the Documentation.

NTrace is made possible through the gracious agreement of DocuSys, Inc. to allow the source for this project to be released to the public for general consumption and improvement, the efforts of Andy Hopper, a Senior Architect with Ipswitch, Inc., and the handy NRefactory library developed by the team that brought you SharpDevelop.

NTrace is released under the Eclipse Public License and is free for all use. If you would like to contribute, please contact one of the project administrators.

Updated Wiki: Documentation

ahopper — Wed, 18 Jan 2012 18:22:50 GMT

Welcome to the documentation for NTrace. We hope that you'll find NTrace to be an invaluable addition to your arsenal of coding tools, and this page is where we will publish information about how to use it, how it works, and tips and tricks for making your life easier.

Launch in another window

Introduction
How to use NTrace
Want to use ETW Tracing in Unmanaged Code? (External link)

New Post: Recommendation for multi-project setup?

ahopper — Thu, 12 Jan 2012 16:45:23 GMT

Hi, Mike-

You can use a provider ID shared across multiple assemblies. In general, the approach I recommend is to think in terms of the logical components you want tracing from, and use that as your guide for what assemblies have what provider IDs; we simply assign a new provider ID per assembly because it is the safest default behavior. By the way, you can also use the trace flags to filter sub-component's trace messages, so that becomes another way to "slice" the trace output.

-Andy

On Tue, Jan 10, 2012 at 10:35 PM, mikemill <notifications@codeplex.com> wrote:

From: mikemill

Andy, I just started looking at NTrace to see if it'll work for one of our larger applications. Right now we have a single web application that's made up of somewhere around 20 DLLs. What's the recommended way to include NTrace in a project like that? One NTrace.ClassicProvider per DLL? Can we share the ETW provider ID across all the projects and have events all show up in one place or will there be a conflict?

thanks, mj

Read the full discussion online.

To add a post to this discussion, reply to this email (NTrace@discussions.codeplex.com)

To start a new discussion for this project, email NTrace@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com