Run/Debug Configuration: Dart Remote Debug
On this page:
- Getting access to the Run/Debug Configuration: Dart Remote Debug dialog
- Dart Unit-specific configuration settings
- Common options
Getting access to the Run/Debug Configuration: Dart Remote Debug dialog
- Make sure the Node.js and Dart plugins are activated. The plugins are not bundled with RubyMine, but they can be installed from the JetBrains plugin repository as described in Installing, Updating and Uninstalling Repository Plugins and Enabling and Disabling Plugins. Once enabled, the plugins are available at the IDE level, that is, you can use them in all your RubyMine projects.
Dart Unit-specific configuration settings
|Host||In this field, specify the host where the Dart application is running.|
|Port||In this field, specify the port for the debugger to communicate with the specified host. The specified port is shown in the Command line arguments for the remote Dart VM read-only field. Note that the application must be started exactly with these arguments, so do not forget to provide this information to the one who will start it on the remote host or specify the arguments in the Dart Remote Debug run configuration if you are going to launch the application yourself on the localhost.|
|Search Sources in||From this drop-down list, choose the Dart project to debug if your RubyMine project contains several Dart projects configured as content roots. See Developing Several Dart Projects (Packages) within one RubyMine Project on Preparing for Dart Development.|
|Command Line Arguments for the Remote Dart VM||This read-only field shows the port specified in the Port field. Note that the application must be started exactly with these arguments, so do not forget to provide this information to the one who will start it on the remote host or specify the arguments in the Dart Remote Debug run configuration if you are going to launch the application yourself on the localhost.|
|Alt+Insert||Click this button to add a new configuration to the list.|
|Alt+Delete||Click this button to remove the selected configuration from the list.|
|Ctrl+D||Click this button to create a copy of the selected configuration.|
|Edit defaults||Click this button to edit the default configuration templates. The defaults are used for newly created configurations.|
|or||Alt+Up or Alt+Down||Use these buttons to move the selected configuration or folder up and down in the list.|
|Move into new folder / Create new folder||Use this button to create a new folder. |
If one or more run/debug configurations are in focus, the selected run/debug configurations are automatically moved to the newly created folder. If only a category is in focus, an empty folder is created.
Move run/debug configurations to a folder using drag-and-drop, or the buttons.
|Sort configurations||Click this button to sort configurations in alphabetical order.|
|Name||In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations.|
|Defaults||This node in the left-hand pane of the dialog box contains the default run/debug configuration settings. Select the desired configuration to change its default settings in the right-hand pane. The defaults are applied to all newly created run/debug configurations.|
|Share|| Select this check box to make the run/debug configuration available to other team members. |
The shared run/debug configurations are kept in separate xml files under
This check box is not available when editing the run/debug configuration defaults.
|Single instance only||If this check box is selected, this run/debug configuration cannot be launched more than once. |
Every time a new run/debug configuration is launched, RubyMine checks the presence of the other instances of the same run/debug configuration, and displays a confirmation dialog box. If you click OK in the confirmation dialog box, the first instance of the runner will be stopped, and the next one will take its place.
This makes sense when the usage of certain resources can cause conflicts, or when launching two run/debug configurations of the same type consumes too much of the CPU and memory resources.
If this check box is not selected, it is possible to launch as many instances of the runner as required. So doing, each runner will start in its own tab of the Run tool window.
|Before launch||Specify which tasks must be performed before applying the run/debug configuration. The specified tasks are performed in the order they appear in the list. |