A moment ago, we released the 2022.3 versions of dotTrace, dotMemory, dotCover, and dotPeek. Take a look at the updates and features that are now available.
You can use dotCover on ARM64 CPUs on Windows. This applies to all versions: dotCover standalone, dotCover in Rider, dotCover in Visual Studio, and the dotCover console runner.
Beginning with this release, restarting Unity is no longer required and test coverage in JetBrains Rider is supported out of the box.
You can now use the dotCover console runner on ARM32 CPUs on Linux.
We’ve added the Show Covering Tests action to the dotCover context menus in both the Rider code editor and the Unit Test Coverage window.
Now dotCover copies only the assemblies and symbol files required for continuous testing in both Visual Studio and JetBrains Rider.
In addition to Windows, dotMemory is now available for JetBrains Rider on Linux and macOS. Two new profiling modes – Memory (sampled allocations) and Memory (full allocations) – are available in the Run widget and in the Run | Switch profiler configurations menu.
Now you can use dotMemory on ARM64 CPUs on Windows. This applies to all versions: dotMemory standalone, dotMemory in Rider, dotMemory in Visual Studio, and the dotMemory command-line tool.
Now you can run the dotMemory command-line profiler on ARM32 CPUs on Linux.
The dotMemory command-line profiler now has the --saving-mode argument, which lets you set conditions for when to save a dotMemory workspace.
Now you can use dotTrace on ARM64 CPUs on Windows. This applies to all versions: dotTrace standalone, dotTrace in Rider, dotTrace in Visual Studio, and the dotTrace command-line tool.
You can now run the dotTrace command-line profiler on ARM32 CPUs on Linux.
We’ve added several improvements to snapshot analysis.
