The latest updates on all JetBrains products and topics
In the 2019.2 release, the dotCover team was mainly focused on the console runner tool. The result is some good news about the tool, including one important fix specially for .NET Core users: The dotCover console runner is available not only on Windows, but on macOS and Linux as well. The cons…
dotMemory 2019.2 no longer supports remote profiling. Remote profiling allowed you to profile an application running on a remote computer with dotMemory running locally. So, why did we get rid of it? (more…)…
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 in Rider. (more…)…
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 on Windows. Now, it's time to fill the gap. In Rider 20…
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 from users seeing classes with ...+<>c... in their name…
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 brings some important changes, especially con…
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. As we mentioned back then, this was just the begin…
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. The opposite is true: our team has been investing even more effort…
Important: This post is outdated. Please use the instructions from the dotCover documentation. 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 t…
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 EAP build – the first Rider version ever that featur…
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 no straight and easy workflow for getting …
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 new Unit Test Coverage window, real-time fil…
