Toolset and Build

On this page, you can configure Rider's build process.

Toolset


Mono executable path	You will need to specify Mono executable if you want to build .NET projects on macOS.
.NET Core CLI executable path	Use this option to specify the build executable for .NET Core projects.
Use MSBuild.exe version	Using this selector, you can choose the version of MSBuild.exe that is used to build the solution. You can choose one of the automatically detected MSBuild versions, or specify the path to a custom MSBuild executable in a non-standard location.
MSBuild global properties

Design Time Build (Solution Loading)

When you open a solution, JetBrains Rider launches MSBuild in the background to build the list of files in each project, resolve project references and so on.


Use up to X processes in parallel	In most cases launching MSBuild in a single process results in the fastest solution load times, however sometimes (mostly in large solutions) multiple process can speed up solution load. So if you see the 'Wait for solution synchronisation' status for too long after opening a solution, you can try setting multiple processes in this selector.
MSBuild solution loading targets	If your solution uses some non-standard components defined via MSBuild targets, JetBrains Rider may fail to load these components. A typical symptom of that is unresolved (red) code in some files, but no errors on solution build. In this case, list names of such targets separated with comma in this field.

Use up to X processes in parallel

In most cases launching MSBuild in a single process results in the fastest solution load times, however sometimes (mostly in large solutions) multiple process can speed up solution load.

So if you see the 'Wait for solution synchronisation' status for too long after opening a solution, you can try setting multiple processes in this selector.

MSBuild solution loading targets

If your solution uses some non-standard components defined via MSBuild targets, JetBrains Rider may fail to load these components. A typical symptom of that is unresolved (red) code in some files, but no errors on solution build.

In this case, list names of such targets separated with comma in this field.

Build Engine


Use ReSharper Build	If this checkbox is selected, JetBrains Rider will optimize build process with ReSharper Build, which tracks changes in your solution and only rebuilds modified projects and necessary dependencies. If the checkbox is unselected, Rider will delegate the entire solution build to MSBuild.exe. You may need to disable this option if your solution includes non-MSBuild projects or projects with custom build steps.
Run build after solution is loaded	This self-explanatory option will be applied independently of selected build management preference.

Use ReSharper Build

If this checkbox is selected, JetBrains Rider will optimize build process with ReSharper Build, which tracks changes in your solution and only rebuilds modified projects and necessary dependencies.

If the checkbox is unselected, Rider will delegate the entire solution build to MSBuild.exe. You may need to disable this option if your solution includes non-MSBuild projects or projects with custom build steps.

Run build after solution is loaded

This self-explanatory option will be applied independently of selected build management preference.

Build Parameters


Use up to X processes in parallel	Using this selector, you can choose the number of parallel process used to build the solution.
Restore NuGet packages before build	When this checkbox is selected, JetBrains Rider will restore NuGet packages for all projects in the current solution. Note that this option requires .NET Framework 4.5 or later to be installed on your machine. Rider will only restore NuGet packages if this is allowed by the corresponding options on the Build, Execution, Deployment \| NuGet settings page.
Write log to output	When this checkbox is selected, log items selected under it will be shown in the Build window.
Write to log file	When this checkbox is selected, build output is saved to a log file. Use controls under this checkbox to choose a verbosity level and a path where the log file is saved. If the selected log directory does not exist, it is shown in red. However, JetBrains Rider will create the non-existent path when logging to file for the first time. Note that logging to file does not depend on logging to the Build window.
Invoke Pre- and Post- build event targets for skipped projects	When JetBrains Rider uses heuristics to skip some projects during the build process, such projects are skipped completely, including all additional build logic. Use this checkbox to always execute pre-build and post-build events for all projects. To check and configure Pre- and Post- build events, right-click the project in the Solution Explorer, select Properties, and then choose Build Events.
Invoke BeforeBuild and AfterBuild targets for skipped projects	When JetBrains Rider uses heuristics to skip some projects during the build process, such projects are skipped completely, including all additional build logic. Use this checkbox to always execute BeforeBuild and AfterBuild MSBuild targets.
Pass Visual Studio parameters to the build	If you choose to delegate solution build to MSBuild (the Use ReSharper Build option is not selected), JetBrains Rider will not pass the `$(VisualStudioVersion)` and `$(BuildingInsideVisualStudio)` properties to the MSBuild by default. If these properties are used in your projects, select this checkbox to override the default behavior.

Last modified: 30 September 2021