We’re often asked how ReSharper and Rider relate to build servers, and how their features can be utilized in CI/CD environments. There are actually quite a few tools bundled in free packages – namely ReSharper.CommandLineTools or dotCover.CommandLineTools – that can help to continuously monitor and improve our codebase. In this post, we will discuss the ReSharper tools, which include: InspectCode – runs code analysis to find and report code issues DupFinder – identifies semantically duplicated code fragments CleanupCode – reformats code to make it consistent Check out our blog po

We recently published the Rider 2020.2 roadmap, as well as the ReSharper C++ 2020.2 roadmap, and we’d now like to bring you up to speed with what we’ve got planned for ReSharper 2020.2 in .NET. As ever, please be aware that this list is preliminary. These are the broad areas we’re working on, and a list of our priorities, but things can change before release. With that disclaimer out of the way, let’s take a look at what’s coming! (more…)

We’ve just published ReSharper Ultimate 2019.3.1 hotfix. Come and grab one if you are experiencing any of the issues listed below. (more…)

In 2019.1 release, we’ve reworked the inspections and intention actions related to importing namespaces and using FQN. We’ve also added some PHP-specific intentions to the Code Cleanup tool, which will help you automatically run safe transformations on the whole project or a part of it. (more…)

Along with the latest releases of ReSharper, we have made Code Cleanup part of the ReSharper Command Line Tools. These tools allow us to run several ReSharper features from the command line or as part of continuous integration. Two tools have been there for a while — InspectCode (which can run hundreds of ReSharper code inspections outside of Visual Studio) and dupFinder (which helps finding duplicate code in C# and VB.NET code). The new Code Cleanup command line will apply formatting code style preferences and other improvements such as file layout, removing redundancies, optimizing using,

I bet you'll agree with me that dealing with legacy code is not a pleasant task. Almost like cleaning up an old storage room full of dust and garbage. Even if you have powerful inspections that tell you what's going wrong, you still have to run them manually and then apply quick-fixes one by one on every of the errors you have found. We don't like mundane tasks like that, and that's why in the new IntelliJ IDEA 14 EAP build we're adding the new Code Cleanup feature that automatically fixes your code for you, in one click instead of dozen. To use the feature, simply go to Analyse → Code Clea