Click here to Skip to main content
Click here to Skip to main content

A simple solution to see the inside of your code

, 25 May 2006 CPOL
Rate this:
Please Sign up or sign in to vote.
A simple solution to see the inside of your code.

Introduction

Have you ever wanted to see what happens inside of your code? This project catches in real time every trace message from your application, centralizes them, and shows them on your screen in a friendly way.

The package contains five projects:

  • Tracer is a pipe server, and it receives all the trace messages and shows them on the interface.
  • EsiListener is a custom listener and also the pipe client. It sends all the trace messages to the server.
  • CPPEsiListener a C++ DLL used to send messages to MyTracer.
  • Client is a C# demo application. It can be your application.
  • CPPClient is a C++ demo application.

How it looks

Features

  • It is very easy to add or remove without changing your code.
  • Works with every application which respects standard tracing mode.
  • Works with different applications at the same time.
  • Locates the trace messages inside your application.
  • Traces objects and display all their properties and values.

How to use it

  • The Listener can be added from the source code:
    Trace.Listeners.Add( new Esi.Diagnostics.Listener() );
  • The Listener can be added from your application Config file like shown below:
    <system.diagnostics>  
        <trace>    
          <listeners>    
              <add name="myListener" 
                 type="Esi.Diagnostics.Listener, esiListener"/>    
              <remove 
                 type="System.Diagnostics.DefaultTraceListener"/>
          </listeners>   
        </trace> 
    </system.diagnostics>
  • For tracing, just use the standard tracing:
    Trace.WriteLine( " Hello world :) " ); 
    Trace.Write( "Hello again :P" );
  • If you want MyTracer to recognize your message as an error, information, or warning, use the convention described below:
    • error -> message has to start with [E],
    • warning -> message has to start with [W],
    • information -> message has to start with [I],
    • service -> message has to start with [S] (reserved for MyTracer application),
    • unknown messages -> any other messages.
    Trace.Write( "[E]Uuuups error :( " );
  • An interesting option is that you can trace object values with one call:
    Point p1 = new Point( 5, 5);
    Trace.WriteLine( p1 );
  • If you don't want to copy esiListener.dll in every application directory, you can insert esiListener.dll in the global assembly cache.
    gacutil -i esiListener.dll
  • For C++, copy the EsiListenerCPP.dll near the application. Add in the application project, Diagnostics.h and cpp (Set option: Do not use the precompiled header for the Diagnostic.cpp file). Before starting tracing, call:
    Trace::Init();

    For trace, call:

    Trace::WriteLine("Trace from C++");

    Convention for erorr[E], warning[W], and information[I] works here.

References

  • Inter-Process Communication in .NET Using Named Pipes, Part 1, by Ivan L.
  • TraceListeners and Reflection, by Jerry Dennany.

Others

I have updated this article especially for ninjacross Smile | :) . That's all, and thank you for your attention.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

Maze
Software Developer
Romania Romania
No Biography provided

Comments and Discussions

 
QuestionNice work! However... Pinmemberke4vtw13-May-08 8:21 
AnswerRe: Nice work! However... PinmemberMaze14-May-08 11:30 
GeneralNot thread safe PinmemberNinjaCross29-Sep-05 13:25 
First of all, my best compliments for the good article, it gave me an interesting idea that i hope i'll be able to apply to my current project Smile | :)
I'm writing you because i discovered that compiling and running the project on .NET 2.0 it seems to don't work correctly in UI-involved operations.
In fact, you access the UI controls (such as lstView) from a different thread (uiThread) other than the thread they were created on.
In .NET 1.0/1.1 the error doesn't appear because, as i read somewhere in the MSDN, this kind of cross-thread operation check is not correctly performed by the platform.
I solved modifing the code using BeginInvoke as suggested here[^]. Cool | :cool:
Best regards.
 
--
NinjaCross
www.ninjacross.com
 

GeneralRe: Not thread safe PinmemberMaze20-Oct-05 5:45 
GeneralRe: Not thread safe PinmemberNinjaCross16-May-06 4:18 
JokeRe: Not thread safe PinmemberMaze25-May-06 12:00 
GeneralRe: Not thread safe PinmemberNinjaCross25-May-06 13:13 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web02 | 2.8.141223.1 | Last Updated 25 May 2006
Article Copyright 2005 by Maze
Everything else Copyright © CodeProject, 1999-2014
Layout: fixed | fluid