Merge pull request #185 from PowerShell/release/0.6.1

Prepare 0.6.1 release

Author: daviwil

CHANGELOG.md

@@ -1,5 +1,13 @@
 # vscode-powershell Release History
 
+## 0.6.1
+### Monday, May 16, 2016
+
+- Fixed #180: Profile loading should be enabled by default
+- Fixed #183: Language server sometimes fails to initialize preventing IntelliSense, etc from working
+- Fixed #182: Using 'Run Selection' on a line without a selection only runs to the cursor position
+- Fixed #184: When running a script in the debugger, $host.Version reports wrong extension version
+
 ## 0.6.0
 ### Thursday, May 12, 2016
 

package.json

@@ -1,7 +1,7 @@
 {
     "name": "PowerShell",
     "displayName": "PowerShell",
-    "version": "0.6.0",
+    "version": "0.6.1",
     "publisher": "ms-vscode",
     "description": "Develop PowerShell scripts in Visual Studio Code!",
     "engines": {
@@ -129,7 +129,7 @@
                     "/logLevel:Verbose",
                     "/hostName:\"Visual Studio Code Host\"",
                     "/hostProfileId:Microsoft.VSCode",
-                    "/hostVersion:0.5.0"
+                    "/hostVersion:0.6.1"
                 ],
                 "configurationAttributes": {
                     "launch": {
@@ -191,7 +191,7 @@
                     "/logLevel:Verbose",
                     "/hostName:\"Visual Studio Code Host\"",
                     "/hostProfileId:Microsoft.VSCode",
-                    "/hostVersion:0.5.0"
+                    "/hostVersion:0.6.1"
                 ],
                 "configurationAttributes": {
                     "launch": {
@@ -242,7 +242,7 @@
                 },
                 "powershell.enableProfileLoading": {
                     "type": "boolean",
-                    "default": false,
+                    "default": true,
                     "description": "If true, causes user and system wide profiles (profile.ps1 and Microsoft.VSCode_profile.ps1) to be loaded into the PowerShell session.  This affects IntelliSense and interactive script execution.  The debugger is not affected by this setting."
                 },
                 "powershell.scriptAnalysis.enable": {

src/features/Console.ts

@@ -142,15 +142,20 @@ export function registerConsoleCommands(client: LanguageClient): void {
 
     vscode.commands.registerCommand('PowerShell.RunSelection', () => {
         var editor = vscode.window.activeTextEditor;
-        var start = editor.selection.start;
-        var end = editor.selection.end;
-        if (editor.selection.isEmpty) {
-            start = new vscode.Position(start.line, 0)
+        var selectionRange: vscode.Range = undefined;
+
+        if (!editor.selection.isEmpty) {
+            selectionRange =
+                new vscode.Range(
+                    editor.selection.start,
+                    editor.selection.end);
+        }
+        else {
+            selectionRange = editor.document.lineAt(editor.selection.start.line).range;
         }
+
         client.sendRequest(EvaluateRequest.type, {
-            expression:
-            editor.document.getText(
-                new vscode.Range(start, end))
+            expression: editor.document.getText(selectionRange)
         });
     });