ReSharper Ultimate 2017.1 EAP 7: usability improvements to Code Cleanup

As we approach the release date, there’s always an urge to get more bugs fixed and new features polished. Obviously, we couldn’t resist and decided to publish an additional pre-release build. Download ReSharper Ultimate 2017.1 EAP 7 and check some nice new features and improvements we have introduced.

Throughout this Early Access Program, we’ve been working on improving the design and usability of ReSharper’s Code Cleanup. This feature is useful when you need to apply a number of code cleanup tasks in a bulk mode. You can create various code cleanup profiles to apply in different scenarios.

In previous ReSharper versions, you had to go to Code Editing | Code Cleanup to configure the profiles. Now you can create and edit your custom task-specific profiles right in the Code Cleanup dialog box, simply by pressing Ctrl+E,C.

We’ve also expanded the list of C++ code cleanup tasks with ReSharper’s 14 most commonly used code style features.

Code Cleanup dialog box

In the previous EAP build, we introduced an option to filter the results in the Go to Everything popup. EAP 7 adds a similar option to the Go to Text popup. Type ‘/’ and some designated chars to use the filter:

Filter in Go to Text

Apart from these features, we’ve fixed several bugs in ReSharper and ReSharper C++.

The 2017.1 release is just around the corner, so please stay tuned for the news!

This entry was posted in How-To's and tagged , , . Bookmark the permalink.

8 Responses to ReSharper Ultimate 2017.1 EAP 7: usability improvements to Code Cleanup

  1. What about the code cleanup command line tool?

  2. Pingback: ReSharper Ultimate 2017.1 – Alles zur neuen Version

  3. Pingback: Dew Drop - March 29, 2017 (#2450) - Morning Dew

  4. Marko Lahma says:

    Seems that NUnit test detection has broken in this version. Can no longer run NUnit tests/tests are not detected in source code. Worked fine with EAP 6.

  5. Sergio Pedri says:

    Awesome! I was wondering if the suggested annotations to mark that a method can throw an exception (so that it should be put inside a try/catch block, or not awaited directly if async) and the annotation to mark that a method never throws (so that resharper could tell it’d be useless to put it inside a try/catch block) made it into this upcoming 2017.1 release.
    Keep up the good work!

Leave a Reply

Your email address will not be published. Required fields are marked *