A new TraceListener in Orcas: EventSchemaTraceListener [Inbar Gazit]

re: A new TraceListener in Orcas: EventSchemaTraceListener [Inbar Gazit]

Bruce — Sat, 10 Mar 2007 07:01:28 GMT

If you're using orcas, can't you just say:

var myTraceSource = new System.Diagnostics.TraceSource("MyTraceSource");

re: A new TraceListener in Orcas: EventSchemaTraceListener [Inbar Gazit]

DanielMoth — Sat, 10 Mar 2007 13:18:06 GMT

Bruce, just because you *can* doesn't mean that you *should* and it certainly doesn't mean that you *must* use local type inference :)

re: A new TraceListener in Orcas: EventSchemaTraceListener [Inbar Gazit]

alikl — Mon, 12 Mar 2007 23:22:57 GMT

Very, Very nice feature!!

I gives customers to build systmes and then define what to audit no matter what dictates it - perf issues, debugging, or compliance like SOX, PCI, and others. i am taking it too far :)?

re: A new TraceListener in Orcas: EventSchemaTraceListener [Inbar Gazit]

renaud — Tue, 13 Mar 2007 02:21:16 GMT

Could you please elaborate on where/how the schema for the events is specified? Also what happens if an event does not match the schema?

Thank you.

re: A new TraceListener in Orcas: EventSchemaTraceListener [Inbar Gazit]

Inbar Gazit — Tue, 13 Mar 2007 20:03:24 GMT

The schema for the listener is specified in a validation file - event.xsd (this is a schema file) that describes the different elements of the event that the listener will listen to. . The XSD is available from the Vista Platform SDK available here: http://www.microsoft.com/downloads/details.aspx?FamilyId=C2B1E300-F358-4523-B479-F53D234CDCCF&displaylang=en

There shouldn't be any issue if the event mismatches the schema, unless validation is actually run on the resultant output. Tools that may be relying on certain elements in the schema will naturally not run if those elements are not present.

Watch out: DebugView (OutputDebugString) & Performance

Darren Jefford — Tue, 03 Apr 2007 23:58:48 GMT

For developer level tracing the tracing classes held within the System.Diagnostics namespace are often

.NET Framework 3.5 Now Available! [Justin Van Patten]

BCL Team Blog — Tue, 20 Nov 2007 03:48:15 GMT

.NET Framework 3.5 and Visual Studio 2008 have officially shipped! Soma has the announcement on his blog