3
3
This document contains troubleshooting steps for commonly reported issues when using the
4
4
PowerShell extension for Visual Studio Code.
5
5
6
- ## Mac OS X
6
+ ## Windows
7
+
8
+ ### 1. IntelliSense is extremely slow on PowerShell 5.0
9
+
10
+ There is a known issue with PowerShell 5.0 which, for a small number of users, causes IntelliSense
11
+ (code completions) to return after 5-15 seconds. The following steps * might* resolve the issue for you:
12
+
13
+ 1 . In a PowerShell console, run the following command: ` Remove-Item -Force -Recurse $env:LOCALAPPDATA\Microsoft\Windows\PowerShell\CommandAnalysis `
14
+ 2 . Restart Visual Studio Code and try getting IntelliSense again.
15
+
16
+ This issue has been resolved in PowerShell 5.1.
17
+
18
+ ## macOS (OS X)
7
19
8
20
### 1. PowerShell IntelliSense does not work, can't debug scripts
9
21
10
- The most common problem when the PowerShell extension doesn't work on Mac OS X is that
22
+ The most common problem when the PowerShell extension doesn't work on macOS is that
11
23
OpenSSL is not installed. You can check for the installation of OpenSSL by looking for
12
- the following two files:
24
+ the following files:
25
+
26
+ If installed using Homebrew:
27
+
28
+ ```
29
+ /usr/local/opt/openssl/lib/libcrypto.1.0.0.dylib
30
+ /usr/local/opt/openssl/lib/libssl.1.0.0.dylib
31
+ ```
32
+
33
+ If installed by some other means:
13
34
14
35
```
15
36
/usr/local/lib/libcrypto.1.0.0.dylib
@@ -21,17 +42,15 @@ do not have OpenSSL installed.
21
42
22
43
#### Installing OpenSSL via Homebrew
23
44
24
- You can use [ Homebrew] ( http://brew.sh ) to easily install OpenSSL. First, install Homebrew and then run the following command:
45
+ We ** highly recommend** that you use [ Homebrew] ( http://brew.sh ) to install OpenSSL. The PowerShell distribution for macOS
46
+ has built-in support for Homebrew's OpenSSL library paths. If you install with Homebrew, you will avoid
47
+ [ security concerns] ( https://github.com/PowerShell/PowerShell/blob/master/docs/installation/linux.md#openssl )
48
+ around creating symbolic links in your ` /usr/local/lib ` path which are needed when using other means of installation.
25
49
26
- ```
27
- brew install openssl
28
- ```
29
-
30
- After installation, the libraries of interest must be symlinked to ` /usr/local/lib ` ; e.g. (note that /usr/local/lib may not already exist and may need to be created before symlinking):
50
+ First, install Homebrew and then run the following command:
31
51
32
52
```
33
- ln -s /usr/local/opt/openssl/lib/libcrypto.1.0.0.dylib /usr/local/lib/libcrypto.1.0.0.dylib
34
- ln -s /usr/local/opt/openssl/lib/libssl.1.0.0.dylib /usr/local/lib/libssl.1.0.0.dylib
53
+ brew install openssl
35
54
```
36
55
37
56
Restart VS Code after completing the installation and verify that the extension is working correctly.
@@ -47,8 +66,8 @@ sudo port install openssl
47
66
You will need to take an additional step once installation completes:
48
67
49
68
```
50
- sudo ln -s /opt/local/lib/libcrypto.1.0.0.dylib /usr/local/lib/
51
- sudo ln -s /opt/local/lib/libssl.1.0.0.dylib /usr/local/lib/
69
+ sudo ln -s /opt/local/lib/libcrypto.1.0.0.dylib /usr/local/lib/libcrypto.1.0.0.dylib
70
+ sudo ln -s /opt/local/lib/libssl.1.0.0.dylib /usr/local/lib/libssl.1.0.0.dylib
52
71
```
53
72
54
73
Thanks to [ @MarlonRodriguez ] ( https://github.com/MarlonRodriguez ) for the tip!
0 commit comments