Since a refactoring is an operation that may affect many files and bring out changes that
may break compilation or conflict with existing code, ReSharper performs a special check before applying
During this check ReSharper looks for possible problems (such as duplicate names, visibility conflicts,
and displays the list of encountered conflicts (on the last step before applying the refactoring).
If conflicts are found, the refactoring will not proceed unless you do one of the following:
- Click Next to ignore the conflicts. In this case the refactoring will be applied, but that may produce uncompilable code.
Click a link in the list to navigate to the problematic lines of code and make necessary fixes.
TipFor some conflicts quick-fixes are suggested.
- Click Cancel to stop the refactoring operation, no changes will be made.