ReSharper 2022.1 Starts Early Access Program!
Please welcome the first EAP build of ReSharper 2022.1! This iteration is a little different for us in terms of planning, and we thought it would make sense to share our plans with you.
Our usual plan for the release is first to make features, then to fix bugs. Usually, we dedicate the first third, or even half, of the release time, to developing new features or reworking the existing ones – adding new logic, implementing new settings, rewriting mechanisms under the hood, etc. After that, we fix the bugs and address the issues in the features that were just added and any older issues remaining in the issue tracker.
This time we’ve decided to try a different approach. There are several directions that the team will continue working on, like language support and the “out of process” mode. But for other parts of ReSharper, we’ve decided to devote this whole iteration to addressing quality and bug fixes. There will be some new additions that we already began working on before this crusade for quality was decided. However, the major news for this release will be about bug fixes, QA challenges, and performance investigations. Let’s take a look at what we’ve done already!
- We’ve fixed the problem of event buffer overflow (also known as “massive file system change”). ReSharper listens to changes in the file system using an API that accepts a buffer to be filled with the change that happened. If the change is big enough (like when many files changed when updating from the VCS or build), the buffer size might not be sufficient to accommodate the change. ReSharper interpreted this situation like “something changed, but I cannot tell exactly what”, and thus rechecked all the files if they were changed. There is now no more of that redundancy!
- We’ve fixed the support for .sqlproj files in localized Visual Studios (RSRP-487192).
- We’ve fixed the issue that caused code cleanup to remove all
@usingdeclarations from .razor files that contain Blazor components (RSRP-485772).
- We’ve fixed the behavior of If To Switch and Invert If context actions for Razor code that contains references to Blazor components.
- We’ve added the Metadata tree view, that may already be familiar to dotPeek users, into ReSharper, but only for Visual Studio 2022.
- We’ve improved C# 11 support: ReSharper is now aware of generic attributes.
For the full list of resolved issues, please refer to our bug tracker.
ReSharper C++ quality-focused release has Unreal Engine support as the top priority, so the first EAP build brings several important Unreal-related fixes. Check out this blog post for details.
As a bonus, we’ve also added a new way to quickly consult the Unreal Engine documentation about the details of some class, symbol, or function. You can now click Read more in the Quick Documentation pop-up (
Ctrl+Shift+F1) to open the corresponding page in your browser.
We’ve added support for the .NET Core NetTrace file format. NetTrace files can be collected with the
dotnet-trace collect command. Afterwards, dotTrace will convert them to its snapshot format and present them in the Timeline viewer.
When the command line tool saves the snapshot data, it may be unclear how long you have to wait. We have added a visual indication of progress. Now the size of the already written data is shown during saving.
We’re interested in your feedback! Please don’t hesitate to share it in the bug tracker, in the comments section below, or on social media.
Subscribe to Blog updates
Thanks, we've got you!