Move to Resource refactoring
It is a common practice to store localizable strings in resource files when working on project internalization. ReSharper detects strings to be localized and highlights them, so you can easily find and move such strings from your source code to resource files. ReSharper will declare the corresponding resource entry and replace the string in the code with a resource usage.
There are two algorithms that can be applied when ReSharper searches for localizable strings:
If the Pessimistic algorithm is chosen,
ReSharper looks for localizable strings in all elements, except those which have attribute
If the Optimistic algorithm is chosen, ReSharper analyzes only elements with attribute
Localizable(true). Depending on these settings, ReSharper defines whether a
specific string is localizable,
localizable strings and enables the
By default, the Optimistic algorithm is selected. To change the algorithm for the project, click Pessimistic in the Localizable Inspector list in the Properties window. To access this window, select the project node in the Solution Explorer, and then choose in the main menu.
To move string to resource
- Place the caret at the string that should be localized.
- If a string is highlighted, you can use the corresponding quick-fix. Otherwise, choose in the main menu or press F6.
In the Move to resource dialog that appears, ReSharper automatically generates the name for the resource entry and proposes a resource file. If necessary, you can change the name in the Name text box and choose other resource file in the Resource File drop-down list.
- Optionally, you can change the resource string value in the Value text area and add a comment in the Comment text area.
- Optionally, you can specify whether to search for identical strings and the search scope by selecting the value in the Find identical items in drop-down list.
- Click Next to apply the refactoring.
- If you selected the Find identical items in option and ReSharper finds any matching strings defined within the specified scope, you will be able to choose which of these strings should be replaced with usages of the new resource.
ReSharper provides the same functionality for
and its inheritors. Pay attention, that
access modifier in the
file should be
Public, otherwise, the refactoring will not be available.
After the new resource is created you can override its value for other cultures. For more information, see Override Resource Entry.
This feature is supported in the following languages/technologies:
The instructions and examples given here address the use of the feature in C#. For details specific to other languages, see corresponding topics in the ReSharper by Language section.