JetBrains Rider
 
2024.3
Shortcuts: Visual Studio 2022 (Windows)
Get JetBrains Rider
  1. Run, debug, test, deploy
  2. Running
  3. Run native executables

Run native executables

Last modified: 11 February 2024

If you need to launch a native (non-.NET) executable as a part of your testing or debugging session, you need to configure the startup properties of the target executable in a run configuration and then launch it together with another configuration that executes your .NET code as multiple targets.

tip

Note that you cannot debug a native executable. If you have a .NET executable without sources that you want to debug, you can do that with the .NET Executable configuration.

Create a run configuration for native executable

  1. Open the Run/Debug Configuration dialog in one of the following ways:

    • Select Run | Edit Configurations from the main menu.

    • With the Navigation bar visible (View | Appearance | Navigation Bar), choose Edit Configurations from the run/debug configuration selector.

    • Press CtrlAltShift0R and then press 00.

  2. In the Run/Debug Configuration dialog, click Add New Configuration Add New Configuration Ctrl0N, choose the Native Executable configuration type, and specify a name that will help you identify this configuration in the future.

  3. Optionally, adjust the common settings of the configuration and configure before launch tasks.

  4. Specify the path to the target executable.

  5. Optionally, specify program arguments that will be passed to the executable when the configuration is started. Multiple arguments should be separated with whitespaces.

  6. Optionally, specify a custom working directory, otherwise the directory of the target executable will be used.

  7. Optionally, specify custom environment variables for the target executable in the following format:

    envVar1=value1;envVar2=value2

  8. By default, the output of .NET and Mono applications is shown in the Run or Debug window. You can select Use external console to show the output in an external window.

    Note that this checkbox does not affect classic .NET application types (for example, .NET Console Application) — their output in always shown in an external window.

  9. Click Apply to save the configuration.