Configure Project-Specific Properties
The main set of ReSharper preferences (configured in the ReSharper | Options dialog) apply either globally or per solution. There are also some preferences that can be configured for each project or folder separately. These preferences are available in the Project Item Properties popup, which you can invoke by selecting Edit project item properties from the context menu of the project in the Solution Explorer.
Similarly to other ReSharper settings, project-specific properties can be saved in two files: [ProjectName].csproj.DotSettings (intended for common preferences, like C# version) and [ProjectName].csproj.DotSettings.user (intended for personal preferences, like local path mapping). If necessary, you can share the common preferences with your team by putting the [ProjectName].csproj.DotSettings file under source control.
When you edit project-specific settings from the UI, they are saved in the [ProjectName].csproj.DotSettings file.
Only available on folders.
By default, ReSharper assumes that the namespace each class appears in matches its location in the project. The 'root' namespace for the project is defined in the project properties:
As a result of the above, all code elements at the project level are expected to appear in the
Namespaces are made deeper with the introduction of folders. In the example below, a folder called
|Additional assembly references||If your project references some assemblies in a custom way, ReSharper may not be able to find them and therefore cannot correctly analyze this project. |
Use this semicolon-separated list to let ReSharper know where those assemblies are located, so that it could correctly resolve symbols from those assemblies.
|Additional compile items||If your project includes files in a custom way, ReSharper may not be able to find them and therefore cannot correctly analyze this project. |
Use this semicolon-separated list to let ReSharper know where those files are located, so that it could correctly resolve them.
|C#/VB Language Level||Use this selector to choose the language version. The Default value means that ReSharper automatically detects the language version based on the project settings. Depending on the selected language version, ReSharper's code inspection detects code issues and suggests improvements relevant to the selected version.|
|ConfigureAwait analysis mode|
Use this option to analyze
For details, see ConfigureAwait analysis.
|Force call MsBuild||Use this option to retrieve module references via MsBuild. For example, this may be helpful if there are COM API references and the project is opened in an older Visual Studio version, without Roslyn support.|
|Custom pageParseFilterType handling||This property is only available for web projects. |
Use this selector to choose how ReSharper should treat unrecognized values of the
|Localizable||This preference defines whether to perform localization inspection. If the Default value is selected, the inspection is only performed if there is at least one resource file in the project. The Yes and No values allow enabling/disabling this inspection explicitly.|
|Localizable inspector|| The Localizable Inspector project property defines how to treat string literals that are not consumed by any member marked with |
|Read project model from project file|
For most of its features (including navigation, code analysis, refactorings, and code completion), ReSharper builds and maintains a model of the current solution. The model is cached and then used to instantly access any item in the solution structure.
By default, ReSharper reads project and solution files independently of Visual Studio. This method is preferred because:
However, it has some minor side effects:
If some of the above is a problem, set this option to False to make ReSharper read project structure via Visual Studio COM API, which can be a little bit slower.
|Path mapping||This property is only available for web projects. |
Using this preference, you can synchronize locations of files during the design of the app with the locations where the app gets deployed. For more information, see Path mapping.
|Solution-Wide Inspections||This preference defines whether the Solution-wide code inspections should be enabled in the project. The On and Off values allow enabling/disabling this inspection explicitly. The Internal symbols only value partly enables this inspection for types and type members with the internal access. |
Note that this preference only applies if the Solution-wide analysis is enabled.
|Use Roslyn to obtain project references||Starting from Visual Studio 2015, ReSharper retrieves project references via Roslyn. If some references are not resolved correctly, you can disable this option so that the references are retrieved via COM API.|