dotCover 1.0 and dotTrace 4 Performance are Released!
There’s joy and happiness all around for .NET developers as we’re finally releasing dotTrace 4 Performance and dotCover to the market!
Just as a reminder, dotCover is a brand new, simple .NET code coverage tool that:
- Integrates with Visual Studio 2005, 2008, or 2010 to analyze unit test coverage in .NET Framework and Silverlight applications.
- Supports multiple unit testing frameworks (MSTest, NUnit, xUnit, MSpec, etc.)
- Highlights code that is covered (or not covered) by unit tests.
- Provides code coverage via application execution.
- Detects which unit tests cover any particular location in code.
- Integrates with ReSharper’s unit testing toolset.
- Provides a console utility, enabling to use it with a Continuous Integration server.
- Generates XML-based code coverage reports.
dotTrace 4 Performance helps .NET developers:
- Get accurate info on performance bottlenecks in a variety of .NET applications including those built using .NET Framework 4, .NET Compact Framework 3.5, and Silverlight 4.
- Profile applications with great accuracy in several modes, including profiling remote applications.
- Profile complex desktop and server applications, thanks to unprecedented robustness.
- Immediately estimate how removing a particular bottleneck would affect the overall application performance.
- Launch profiling from Microsoft Visual Studio and quickly switch back to review problematic source code.
dotTrace 4 Memory is expected to come out in several months. Meanwhile, dotTrace 3.5 Memory is available, which is a memory part from dotTrace 3.1 with additional support for CLR 4.
dotTrace 4 Performance comes in two editions, Standard and Professional. You can learn more about the new editioning scheme in dotTrace FAQ.
If you’re an existing dotTrace customer, then bang! dotTrace 3.5 Memory is free for you. Better yet, if your license was purchased on or after December 17, 2008, you get a free upgrade to dotTrace 4 Performance and dotTrace 3.5 Memory.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)