Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Edit in VS Code always opens in VS Code vs. VS Code Insiders #1460

Closed
Tracked by #1465 ...
rukiafarraj opened this issue Feb 16, 2022 · 3 comments
Closed
Tracked by #1465 ...

Edit in VS Code always opens in VS Code vs. VS Code Insiders #1460

rukiafarraj opened this issue Feb 16, 2022 · 3 comments

Comments

@rukiafarraj
Copy link

rukiafarraj commented Feb 16, 2022

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

  1. In an Azure Machine Learning workspace, with compute instance running
  2. Navigate to Notebooks
  3. Open or create a new notebook
  4. In the global toolbars, click "Edit in VS Code"

Specifications

  • Version:
  • Platform:
@tbombach
Copy link
Member

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://

@rukiafarraj
Copy link
Author

Thanks, Thomas - this is a good workaround for now unless we start to get additional feedback.

@shsuman
Copy link
Member

shsuman commented Apr 4, 2022

Closing this for now. Please reopen if need be :)

@shsuman shsuman closed this as completed Apr 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants