- Code Inspection
- Resolving global variables
- Making ReSharper ignore specific code
Resolving global variables
ReSharper highlights usages of undefined variables as warnings. There are cases, however, when these usages are valid. For instance, some variables can be defined directly in the markup.
One way to deal with this, is to disable or suppress the corresponding code inspection. However, you can define such variables using the
// global comment. In this case, the inspection will stay active and help you to find typos in variable names.
You can place these comments either at the top of the current file or use a single file for all global variables of the project. Each variable requires a new comment, e.g.:
// global variableName
Create from usage
This is one of the most useful quick-fixes. Whenever you use anything that was not declared, ReSharper can help you create a valid declaration taking into account the usage and the surrounding context.
Specify qualifier explicitly
In case an explicit qualifier is missing, use this quick-fix to add a qualifier.
Declare local variable
When ReSharper finds out that a variable has been assigned without being declared, use this quick-fix to transform the assignment into a variable declaration.
Making ReSharper ignore specific code
ReSharper allows you to ignore specific files, folders and file masks in different ways. You can configure ignored files on the following options pages:
- to exclude files, folders, and masks from code inspection.
- to partly disable code inspection for generated code.
- to specify files and folders that should be ignored by Navigation by Name commands.