Quick-Fixes for Code Issues

Apply quick-fixes

Quick-fixes are visually displayed as action indicators to the left of a highlighted code issue. These indicators appear when you set the caret at the code issue. The following indicators imply quick-fixes:

• — suggests a quick-fix for the detected code issue with the Error severity level.

• — suggests to find an unresolved type or namespace in the NuGet package gallery,

• — suggests an inplace refactoring or a refactoring that can fix the detected code issue.

• — suggests a quick-fix for the detected code issue with Warning, Suggestion or Hint severity level.

• — suggest a Visual Studio's code correction or refactoring action.

• — suggests a quick-fix for redundant code that can be safely removed.

In most cases, a quick-fix is applied immediately. However, some quick-fixes (for example, Change All) require user interaction to choose how exactly they transform your code. In these cases, a Hot Spot Session is deployed in the editor, where you can select one of the suggested values or provide your own values in the active input positions:

To complete the hot spot session:

• If ReSharper suggests some values for the current parameter, use Up and Down arrow keys to navigate through the list of suggested values, or just type in a desired value.

• Press Tab or Enter to accept the value and move to the input position of the next parameter. If this is the last parameter, the hot spot session completes and the caret moves to the end position defined for the session.

• Press Shift+Tab to move the input focus to the input position of the previous parameter.

• Press Esc to exit the hot spot session. In this case, all session parameters will be initialized with default values.

Some quick fixes can be applied not only in the current caret position, but in a larger scope. For more information, see Fix in Scope.

tip

The list of predefined quick-fixes can be extended with custom code inspections defined in the structural search and replace patterns.

Quick-fixes from Visual Studio

Starting from version 2015, Visual Studio comes with its own code analysis engine (Roslyn) and provides its own light bulbs feature to perform quick actions including refactoring and fixing errors.

Visual Studio's quick actions often perform the same fixes as ReSharper's quick-fixes, context action, or refactorings. Therefore, for some errors you may have two similar suggestions from Visual Studio and from ReSharper. In the illustration below, you can see two bulbs both suggesting to remove redundant using directives:

To avoid this, ReSharper provides the Hide Visual Studio light bulb option on the Environment | Editor | Visual Studio Features page of ReSharper options. This option is enabled by default, so you will not see the duplicated bulbs unless you disable it.

If Visual Studio Light Bulb is suppressed, Visual Studio actions can be integrated into ReSharper's action list by selecting the Merge Visual Studio light bulb actions into ReSharper action indicator checkbox. If it is selected, ReSharper does the following for each Visual Studio's quick action:

• If there is a similar ReSharper's quick-fix or context action, the Visual Studio's quick action is not displayed.

• If there are no similar ReSharper's action, the Visual Studio's action becomes available in the ReSharper's action list. You can recognize Visual Studio's quick actions by the special icon .