ReSharper Help

Refactorings for ASP.NET

In ASP.NET, ReSharper supports the Main Set of Refactorings, which are available for C# and Visual Basic .NET code inside ASP.NET files, as well as the Localization Refactorings, which are available for resource usages. There are also some refactorings that are specific to ASP.NET:

To perform a refactoring

  1. Set your caret at a symbol, select a code fragment that you want to refactor, or select an item in a tool window.
  2. Do one of the following:
    • On the main menu, choose ReSharper | Refactor, and then select a desired refactoring.
    • In the editor, File Structure window, or other ReSharper window, right-click the item you want to transform, choose Refactor from the context menu, and then select the required refactoring.  
    • On the main menu, choose  ReSharper | Refactor | Refactor This, or press Ctrl+Shift+R to display the list of applicable refactorings, and select one of them. You can also choose Refactor This in the context menu of a selection.
    • If a refactoring could fix a code issue that ReSharper detects and highlights in the editor, the corresponding action indicator Coding_Assistance__Context_Actions__icon_refactor appears to the left of the code issue. You can click on this indicator or press Alt+Enter to check the suggested refactoring and apply if if necessary.
    • Use default keyboard shortcuts assigned to specific refactorings, or assign custom shortcuts to your favorite refactorings.
  3. If the selected refactoring requires user input, the refactoring wizard opens. Note that the wizard's dialog boxes are not modal, so you can edit the code while the wizard is open.
    To roll back refactoring actions, the wizard provides the option  To enable Undo, open all files with changes for editing. If you select this option, ReSharper opens all modified files in new editor tabs and enables you to roll the refactoring back. In this case, you will need to save the changes yourself. If this option is not selected, ReSharper saves modified files automatically, without opening them.
  4. If a refactoring operation would cause code conflicts (such as duplicate names, visibility conflicts, etc.), the wizard displays the list of conflicts on the last step, before you apply the refactoring. For some conflicts, the wizard can also suggest quick-fixes. For more information, see Resolving Conflicts in Refactorings.

Some refactorings are available immediately after you modify code in the editor. For more information, see Inplace Refactorings

Extract Style

This refactoring allows extracting inline styles as well styles defined in the <style> tag and place them under the specified selectors.

Extract Style refactoring in HTML

In the refactoring wizard, you can change the selector if necessary and select the styles to be extracted:

Extract Style refactoring in HTML

Move to Resource

ASP.NET enables you to create pages that can change content depending on the explicit choice of language, for example. Content and other data are stored in resource files and can be accessed easily using the appropriate resource expressions. If there are some strings, texts hidden in markup, ReSharper helps you find them and accurately transfer to the appropriate resource files without unnecessary complications.

Web_Development__Refactorings__Move_to_Resource
As usual, you just press Ctrl+Shift+R to display the list of all available refactorings and choose the desired one.

Rename

One of the nicest and at the same time the most annoying actions when doing it manually is the Rename refactoring. This refactoring provides an easy way to rename symbols and types and it doesn't matter where the refactoring is invoked and what language is used. So you can change the name of a JavaScript function, rename a C# method, a class or even a namespace and be sure that all usages will be updated correspondingly. You can also change the value of a control identifier in markup, so that all references will be updated everywhere, etc.

Web_Development__Refactorings__Rename

Safe Delete Resource

As soon as you've noticed that some resource is useless, you can invoke the Safe Delete Resource refactoring and remove it immediately.

Web_Development__Refactorings__Safe_Delete_Resource
For more information, see Localization Refactorings.

See Also

Last modified: 30 June 2015