Debugging with JetBrains Chrome Extension
You no longer need to install and use the JetBrains IDE Support Extension for Chrome to debug your applications in JetBrains Rider. However, you can still use it if you want to start a debugging session in the same Chrome instance. By default, JetBrains Rider opens a new window with a custom Chrome user data, see Starting a debugging session with your default Chrome user data.
To install the JetBrains Chrome extension
Open the JetBrains IDE Support page in Chrome Web Store.
Click the Add to Chrome button , and then click Add in the Confirm New Extension dialog that opens. The Add to Chrome button changes to Added to Chrome .
To enable Live Edit and debugging with the JetBrains Chrome extension
In the Settings/Preferences dialog Ctrl+Alt+S, click Debugger under Build, Execution, Deployment, and then click Live Edit. The Live Edit page opens.
Select the Use JetBrains IDE Support extension for debugging and Live Edit checkbox.
To activate, de-activate, and uninstall JetBrains Chrome extension
Control over the JetBrains Chrome extension is provided through the chrome://extensions page. To open the page, just type
chrome://extensionsin the Chrome address bar. Alternatively click Customize and control Google Chrome (), choose Settings from the context menu, and then click Extensions on the chrome://settings page that opens.
To deactivate the extension, clear the Enabled checkbox. The checkbox name changes to Enable.
To activate the extension, select the Enable checkbox.
To uninstall the extension, click the Remove from Chrome button .
To specify the actual JetBrains Rider port in the Chrome extension options
During a debugging session, the Chrome extension listens to the port of the JetBrains IDE from which the extension was invoked. Each IDE including JetBrains Rider has its own default port on which it starts.
If for some reason the default JetBrains Rider port is already busy, JetBrains Rider finds the closest available port and starts on it. This results in a conflict: JetBrains Rider is running on a "new" port while the Chrome extension still listens to the port of a previously started product.
The conflict reveals when you initiate a debugging session with Live Edit: the extension fails to connect through the default port, JetBrains Rider waits for connection from the extension and displays the following message with the port number where it is actually running (for example, current port 63342):
Right-click and choose Options on the context menu. A web page with the Chrome extension options opens showing the parameters to connect to JetBrains Rider.
In the IDE Connection area, specify the actual JetBrains Rider port in the Port spin box.
To override the default CORS settings
Suppose the page you are debugging with Live Edit requests a resource which is, for security reasons, protected against access through CORS settings. You can enable access to the protected resources by changing the Chrome extension options.
Right-click and choose Options on the context menu. A web page with Chrome extension options opens showing the parameters to connect to JetBrains Rider.
In the Force CORS text box, type the pattern that defines the URL addresses you want to make accessible, for example: http://youtrack.jetbrains.com/rest/*.