You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've had some discussions about how VS Code insiders would be supported. From a technical standpoint, our extension does support VS Code insiders. The studio opens VS Code/our extension by using a custom URI format: vscode://. The corresponding URI format for insiders is vscode-insiders:// These get registered with the user's OS, so we don't have a way of responding to one URI format and opening the other version of VS Code.
If this is important to a lot of users, we could work to change the studio UI to add another options to open in VS Code insiders. However, this might confuse users on which to use and could cause confusions if a user is set up in one version (logged in, downloaded extension, etc) but not in the other version.
As a workaround, the user can copy the URL from the studio that opens VS Code and modify it to change vscode:// to vscode-insiders://
Expected Behavior
Launching VS Code from AzureML opens with VS Code Insiders (preview features version)
Actual Behavior
Actually opens in VS Code without preview features, workaround is to search through a really long list to find Insiders.
Steps to Reproduce the Problem
Specifications
The text was updated successfully, but these errors were encountered: