Author Archives: Alexey Totin

Code Coverage on macOS and Linux in Rider 2019.1

Rider 2019.1 brings a lot of good news for macOS and Linux users: our profiling and code coverage tools are now supported (to varying degrees) on macOS and Linux. In this post, we’ll dive deeper into the code coverage updates … Continue reading

Posted in How-To's | Tagged , , , , , | 4 Comments

Profiling Mono and Mono Unity Apps on Windows, macOS, and Linux

Back in Rider 2018.3, we added a performance profiler to Rider. As we try to deliver new features as quickly as possible, the integrated profiler had some limitations: it only supported the profiling of .NET Framework and .NET Core applications … Continue reading

Posted in How-To's | Tagged , , , | 2 Comments

What Do These …<>+c… Classes Do in my Memory Snapshots?

There’s nothing we love as much as user feedback. It is a priceless source of insights into how people use tools like dotMemory, what gets them excited – and what gets them confused. Over the last year we’ve received multiple questions … Continue reading

Posted in How-To's | Tagged , , | 4 Comments

Performance Profiling in Rider 2018.3. What’s New?

If you’re an active Rider 2018.3 user or just follow our blog, you probably know that Rider just got an integrated performance profiler based on JetBrains dotTrace. Though we’ve already reviewed the profiler features on the EAP stage, the release version … Continue reading

Posted in How-To's | Tagged , , | 16 Comments

Performance profiling .NET code in Rider with integrated dotTrace

Important! This post is about an old version of Rider. The profiling workflow is different since Rider 2018.3. Learn more Rider 2018.2 was the first release to host one of our .NET tools, dotCover, together with its unit test coverage features. … Continue reading

Posted in How-To's | Tagged , , | 9 Comments

How does my app allocate to LOH? Find out with dotMemory 2018.2!

If you’re a long-term dotMemory user, you may have noticed the absence of big new features in dotMemory ever since we added support for memory dumps in 2017.2. Rest assured this is not because we’ve lost interest in memory profiling. … Continue reading

Posted in How-To's | Tagged , , , | 3 Comments

> dotnet dotсover test

If you’ve got the idea of this post just by reading the title, you may skip the next paragraph and go right to the procedure. We’re going to talk about the dotCover.exe console runner and a new way to run … Continue reading

Posted in How-To's | Tagged , , , , | 30 Comments

Unit test coverage and continuous testing. Now in Rider!

With each Rider release, we do our best to bridge the gap between Rider and the ReSharper Ultimate bundle. The top in-demand feature has certainly been “Rider + dotCover” integration. So, without further ado, please welcome the latest Rider 2018.2 … Continue reading

Posted in How-To's | Tagged , , , , | 21 Comments

Analyzing code coverage of web apps with the dotCover 2018.1 Console Runner

These days automating unit tests and application coverage is a routine activity in areas like CI and some complex integration testing scenarios. Seeing how most developers work on web applications, it was really annoying that the dotCover console runner had … Continue reading

Posted in How-To's | Tagged , , , , | 16 Comments

dotCover 2018.1: Better continuous testing and more!

In this 2018.1 release, dotCover is by far the product that has received the most changes in the whole .NET tools lineup. These include: Continuous testing with new modes available in any unit test session, Coverage analysis improvements including a … Continue reading

Posted in How-To's | Tagged , , | 20 Comments