In this page of ReSharper options, you can configure preferences of ReSharper Build.
|To build solution, use:||Defines whether native Visual Studio build managment or ReSharper Build is used on build commands, e.g. (Ctrl+Shift+B) as well as for corresponding context menu commands on projects and solution folders in Solution Explorer.|
|Status Bar: show build progress in status bar||If this check box is selected, build progress is displayed in Visual Studio status bar.|
|Task Bar: show build progress in Windows task bar||If this check box is selected, build progress is displayed in the Visual Studio icon on the Windows task bar.|
|Tool Window: when build starts, open the build progress view in a tool window||
When this button is selected, dotCover brings up the ReSharper Build & Run Window to visualize build progress and status.
|Showing build results after build completed||This selector allows you to choose the level of build messages to display build results.|
|Use MSBuild.exe version||Using this selector, you can choose the version of MSBuild.exe that is used to build the solution.|
|Use up to X processes in parallel||Using this selector, you can choose the number of parallel process used to build the solution.|
|Applicable event importance level||This selector allows you to choose the lowest level of MSBuild events displayed ReSharper Build. That is, when the selected value is High (recommended), events with lower importance are filtered out.|
|Projects should be never build||
If you do not need to build some projects when you build your solution, you can exclude them to reduce build time. To do so, mark the projects or solution folders you want to exclude in the Projects should be never built section. You can use the search box in this section to filter the solution tree to show only matching items.
Excluding a project means it won’t get rebuilt, even if source files are out of date or a referenced project has public API changes. This is quite drastic, and can lead to uncaught compilation errors, but can be useful to temporarily exclude a project that is slow to compile, and not used in your current development task. It’s similar to unloading a project in Visual Studio so that it doesn’t compile, but the source files are still available to ReSharper to allow for navigation and refactoring. We recommend reenabling and rebuilding before committing to source control, or using solution-wide analysis to show compile errors as you type.
|Projects should be always build||
ReSharper Build does not build projects if they were built successfully before, and have not had any changes since them. If you need to build some projects independently of changes in them, you can force build them. To do so, mark the projects or solution folders you want to force build in the Projects should be always built section. You can use the search box in this section to filter the solution tree to show only matching items.
Marking a project as 'always build' tells ReSharper Build to never apply heuristics to this project, but to always pass it to MSBuild. This does not mean that the project will always be rebuilt and recompiled, but it means MSBuild is always called - MSBuild will still check timestamps and might perform an incremental build. This is useful for projects that have custom build steps that ReSharper Build can’t track (although it would be better to rewrite the custom build steps as proper MSBuild targets that support incremental build.).