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
[](https://gitter.im/PowerShell/vscode-powershell?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
8
8
9
-
This extension provides rich PowerShell language support for [Visual Studio Code](https://github.com/Microsoft/vscode).
9
+
This extension provides rich PowerShell language support for [Visual Studio Code](https://github.com/Microsoft/vscode) (VS Code).
10
10
Now you can write and debug PowerShell scripts using the excellent IDE-like interface
11
11
that Visual Studio Code provides.
12
12
@@ -66,12 +66,12 @@ You can also install a VSIX package from our [Releases page](https://github.com/
66
66
instructions. The easiest way is through the command line:
[](https://gitter.im/PowerShell/vscode-powershell?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
6
8
7
-
This extension provides rich PowerShell language support for [Azure Data Studio](github.com/Microsoft/azuredatastudio).
9
+
This extension provides rich PowerShell language support for [Azure Data Studio](https://github.com/Microsoft/azuredatastudio) (ADS).
8
10
Now you can write and run PowerShell scripts using the excellent IDE-like interface
9
11
that Azure Data Studio provides.
10
12
11
-
## Platform support
13
+
This extension is powered by the PowerShell language server,
Read the [installation instructions](https://docs.microsoft.com/en-us/powershell/scripting/components/vscode/using-vscode)
38
+
to get more details on how to use the extension on these platforms.
39
+
40
+
**Read the [troubleshooting guide](./docs/troubleshooting.md) for answers to common questions.**
18
41
19
42
## Features
20
43
@@ -27,28 +50,27 @@ Read the [FAQ](https://github.com/PowerShell/vscode-powershell/wiki/FAQ) for ans
27
50
- Document and workspace symbol discovery
28
51
- Run selected selection of PowerShell code using <kbd>F8</kbd>
29
52
- Launch online help for the symbol under the cursor using <kbd>Ctrl</kbd>+<kbd>F1</kbd>
30
-
- Basic interactive console support!
53
+
- Local script debugging
54
+
- Integrated console support
55
+
- PowerShell ISE color theme
31
56
32
57
## Installing the Extension
33
58
34
59
You can install the official release of the PowerShell extension by following the steps
35
-
in the [Azure Data Studio documentation](docs.microsoft.com/en-us/sql/azure-data-studio/extensions).
60
+
in the [Azure Data Studio documentation](https://docs.microsoft.com/en-us/sql/azure-data-studio/extensions).
36
61
In the Extensions pane, search for "PowerShell" extension and install it there. You will
37
62
get notified automatically about any future extension updates!
38
63
39
-
You can also install a VSIX package from our [Releases page](https://github.com/PowerShell/vscode-powershell/releases) and install it through the command line:
64
+
You can also install a VSIX package from our [Releases page](https://github.com/PowerShell/vscode-powershell/releases) by following the
65
+
[Install from a VSIX](https://code.visualstudio.com/docs/editor/extension-gallery#_install-from-a-vsix)
66
+
instructions. The easiest way is through the command line:
In order to use these examples (below), you need to install the SqlServer module from the [PowerShell Gallery](https://www.powershellgallery.com/packages/SqlServer).
97
+
98
+
In order to use these examples (below), you need to install the SqlServer module from the
> NOTE: With version `21.1.18102` and up, the `SqlServer` module supports [PowerShell Core](https://github.com/PowerShell/PowerShell) 6.2 and up, in addion to Windows PowerShell.
87
106
88
-
In this example, we use the `Get-SqlInstance` cmdlet to Get the Server SMO objects for ServerA & ServerB. The default output for this command will include the Instance name, version, Service Pack, & CU Update Level of the instances.
107
+
In this example, we use the `Get-SqlInstance` cmdlet to Get the Server SMO objects for
108
+
ServerA and ServerB. The default output for this command will include the Instance name,
109
+
version, Service Pack, and CU Update Level of the instances.
89
110
90
111
```powershell
91
112
Get-SqlInstance -ServerInstance ServerA, ServerB
92
113
```
93
114
94
115
Here is a sample of what that output will look like:
95
116
96
-
```
117
+
```powershell
97
118
Instance Name Version ProductLevel UpdateLevel HostPlatform HostDistribution
0 commit comments