NTrace is based on ETW(Event Tracing For Windows) which is a kernel-level tracing service which has several benefits over the tracing provided in .NET... Most importantly, it can be turned on and off without restarting the application, but it also has features like built-in high performance circular logging (a circular log is one that never grows above a specified size by flushing out older trace messages), and the ability for you to capture the logs from multiple sources into a single trace session.
A good place to start if you want to do trace or debug messages from .NET, this article explains the differences between trace and debug, how you can turn them on and off, and how you can set them to trace to file or event log without recompiling. Excellent.
New CLR libraries incladd-in hosting model, which was discussed in the last two editions of CLR Inside OutSupport for the Suite B set of cryptographic algorithms, as specified by the National Security Agency (NSA)Support for big integersA high-performance set collectionSupport for anonymous and named pipesImproved time zone supportLightweight reader/writer lock classesBetter integration with Event Tracing for Windows® (ETW), including ETW provider and ETW trace listener APIs
There are are a couple of valuable tricks already in this toolkit:
1) a fix for NUnit (and others) to allow unit testing things which must run in STA mode.
2) a way to make your XAML data binding testable by tracing data binding warnings
All of the tools you need to poke, prod, and monitor your JavaScript, CSS, HTML and Ajax are brought together into one seamless experience, including a debugger, error console, command line, and a variety of fun inspectors.
Group items tagged 
