From 07b996f21a01443bfe390ad75365155dedb000a4 Mon Sep 17 00:00:00 2001 From: Erich Gamma Date: Thu, 6 Jun 2019 09:41:49 +0200 Subject: [PATCH] Update v1_35.md --- remote-release-notes/v1_35.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/remote-release-notes/v1_35.md b/remote-release-notes/v1_35.md index b518082ae..170010e15 100644 --- a/remote-release-notes/v1_35.md +++ b/remote-release-notes/v1_35.md @@ -1,6 +1,6 @@ # May 2019 (version 1.35) -## Remote in VS Code Stable +## Remote Extensions available in VS Code Stable Until now, the remote extensions have only been available when using the Insiders build of VS Code. Now all three remote extensions (SSH, WSL, and Containers) can be used with the Stable 1.35 build of VS Code. @@ -10,10 +10,6 @@ Until now, the remote extensions have only been available when using the Insider In a remote context, [machine scoped settings](https://code.visualstudio.com/updates/v1_34#_machinespecific-settings) can no longer be configured in the User Settings. They can now only be configured in the Remote/Workspace/Folder Settings. See also issue [#2](https://github.com/microsoft/vscode-remote-release/issues/2). -### Extension Packs - -Installing an extension pack in a remote context, which is not tagged as an UI extension, will now install any packed UI extensions in local machine as well. - ## Containers ### "settings" option