Merge branch 'master' of https://github.com/PowerShell/vscode-powershell into PSSA_CheckInnerBraceAndPipe

Author: bergmeister

README.md

@@ -12,7 +12,7 @@ that Visual Studio Code provides.
 - **Linux** with PowerShell Core (all PowerShell-supported distributions)
 - **macOS and OS X** with PowerShell Core
 
-Read the [installation instructions](https://github.com/PowerShell/PowerShell/blob/master/docs/learning-powershell/using-vscode.md)
+Read the [installation instructions](https://docs.microsoft.com/en-us/powershell/scripting/components/vscode/using-vscode)
 to get more details on how to use the extension on these platforms.
 
 Read the [FAQ](https://github.com/PowerShell/vscode-powershell/wiki/FAQ) for answers to common questions.
@@ -38,7 +38,7 @@ In the Extensions pane, search for "PowerShell" extension and install it there.
 get notified automatically about any future extension updates!
 
 You can also install a VSIX package from our [Releases page](https://github.com/PowerShell/vscode-powershell/releases) by following the
-[Install from a VSIX](https://code.visualstudio.com/docs/extensions/install-extension#_install-from-a-vsix)
+[Install from a VSIX](https://code.visualstudio.com/docs/editor/extension-gallery#_install-from-a-vsix)
 instructions.  The easiest way is through the command line:
 
 ```

appveyor.yml

@@ -1,4 +1,4 @@
-version: '1.10.2-insiders-{build}'
+version: '1.10.3-insiders-{build}'
 image: Visual Studio 2017
 clone_depth: 10
 skip_tags: true

docs/development.md

@@ -16,7 +16,7 @@ to before you can proceed.
     Insiders means the extension can be developed ready for new features
     and changes in the next VSCode release.
 
-5. Install [Node.js](https://nodejs.org/en/) 6.0.0 or higher.
+5. Install [Node.js](https://nodejs.org/en/) 8.x or higher.
 
 ## Building the Code
 

docs/ise_compatibility.md

@@ -1,5 +1,13 @@
 # ISE Compatibility
 
+# ATTENTION! THIS DOC HAS MOVED
+
+[THIS DOC IS NOW HOSTED ON DOCS.MICROSOFT.COM.](https://docs.microsoft.com/en-us/powershell/scripting/components/vscode/how-to-replicate-the-ise-experience-in-vscode)
+
+PLEASE REFER TO THE DOC THERE FOR FUTURE REFERENCE AS ANY CHANGES WILL BE MADE TO THAT DOC.
+
+## Summary
+
 While the PowerShell extension for VSCode does not seek
 complete feature parity with the PowerShell ISE,
 there are features in place to make the VSCode experience more natural

docs/remoting.md

@@ -1,5 +1,13 @@
 # PowerShell Remote Editing and Debugging in VSCode
 
+# ATTENTION! THIS DOC HAS MOVED
+
+[THIS DOC IS NOW HOSTED ON DOCS.MICROSOFT.COM.](https://docs.microsoft.com/en-us/powershell/scripting/components/vscode/using-vscode-for-remote-editing-and-debugging)
+
+PLEASE REFER TO THE DOC THERE FOR FUTURE REFERENCE AS ANY CHANGES WILL BE MADE TO THAT DOC.
+
+## Summary
+
 For those of you that were familiar with the ISE, you may recall that you were able to use run `psedit file.ps1` from the integrated console to open files - local or remote - right in the ISE.
 
 As it turns out, this feature is also availible out of the box in the PowerShell extension for VSCode. This guide will show you how to do it.

package-lock.json

@@ -1,7 +1,7 @@
 {
   "name": "PowerShell",
   "displayName": "PowerShell",
-  "version": "1.10.2",
+  "version": "1.10.3",
   "publisher": "ms-vscode",
   "description": "Develop PowerShell scripts in Visual Studio Code!",
   "engines": {
@@ -72,7 +72,8 @@
       "PowerShellCommandExplorer": [
         {
           "id": "PowerShellCommands",
-          "name": "PowerShell Commands"
+          "name": "PowerShell Commands",
+          "when": "config.powershell.sideBar.CommandExplorerVisibility"
         }
       ]
     },
@@ -113,16 +114,20 @@
       },
       {
         "command": "PowerShell.RefreshCommandsExplorer",
-        "title": "Refresh",
+        "title": "Refresh Command Explorer",
         "icon": {
-          "light": "resources/light/refresh.svg",
-          "dark": "resources/dark/refresh.svg"
+          "light": "resources/light/sync.svg",
+          "dark": "resources/dark/sync.svg"
         },
         "category": "PowerShell"
       },
       {
         "command": "PowerShell.InsertCommand",
         "title": "Insert Command",
+        "icon": {
+          "light": "resources/light/pencil.svg",
+          "dark": "resources/dark/pencil.svg"
+        },
         "category": "PowerShell"
       },
       {
@@ -133,6 +138,10 @@
       {
         "command": "PowerShell.ShowHelp",
         "title": "Get Help for Command",
+        "icon": {
+          "light": "resources/light/question.svg",
+          "dark": "resources/dark/question.svg"
+        },
         "category": "PowerShell"
       },
       {
@@ -202,6 +211,16 @@
       }
     ],
     "menus": {
+      "commandPalette": [
+        {
+          "command": "PowerShell.InsertCommand",
+          "when": "false"
+        },
+        {
+          "command": "PowerShell.RefreshCommandsExplorer",
+          "when": "config.powershell.sideBar.CommandExplorerVisibility"
+        }
+      ],
       "editor/context": [
         {
           "when": "editorLangId == powershell",
@@ -224,11 +243,13 @@
       "view/item/context": [
         {
           "command": "PowerShell.ShowHelp",
-          "when": "view == PowerShellCommands"
+          "when": "view == PowerShellCommands",
+          "group": "inline@1"
         },
         {
           "command": "PowerShell.InsertCommand",
-          "when": "view == PowerShellCommands"
+          "when": "view == PowerShellCommands",
+          "group": "inline@2"
         }
       ]
     },
@@ -456,6 +477,11 @@
       "type": "object",
       "title": "PowerShell Configuration",
       "properties": {
+        "powershell.sideBar.CommandExplorerVisibility": {
+          "type": "boolean",
+          "default":true,
+          "description": "Specifies the visibility of the Command Explorer in the PowerShell Side Bar."
+        },
         "powershell.powerShellExePath": {
           "type": "string",
           "default": "",