Shulou(Shulou.com)06/02 Report--

(1) install the PowerShell plug-in in VSCode

You need to search for the installation in the VSCode plug-in Center, as shown in the figure after the installation is complete.

(2) modify the configuration file of VSCode to add support for PowerShell, such as character set, IntelliSense, etc.

Open VSCode, select the file-- "preferences--" settings, and then select the curly braces {} on the right side of the settings interface to configure. The additional configuration is as follows

{

"csharp.suppressDotnetRestoreNotification": true

"editor.renderWhitespace": "all"

"editor.renderControlCharacters": true

"omnisharp.projectLoadTimeout":

"files.trimTrailingWhitespace": true

"files.encoding": "utf8bom"

"files.autoGuessEncoding": true

}

As shown in the figure

After the setup is complete, PS can do IntelliSense, as shown in the figure.

Reference link:

Https://docs.microsoft.com/zh-cn/powershell/scripting/components/vscode/using-vscode?view=powershell-6

(3) automatic integration with GitHub

If your local repository already contains a GitHub repository, and the directory of the repository has been opened in VSCODE, then VSCode will intelligently prompt you whether the warehouse has changed, as shown in the figure.

(IV) valuable links to PS and VSCode integration

Https://devblogs.microsoft.com/scripting/get-started-with-powershell-development-in-visual-studio-code/

Https://devblogs.microsoft.com/scripting/visual-studio-code-editing-features-for-powershell-development-part-1/

Https://devblogs.microsoft.com/scripting/visual-studio-code-editing-features-for-powershell-development-part-2/

Https://devblogs.microsoft.com/scripting/debugging-powershell-script-in-visual-studio-code-part-1/

Https://devblogs.microsoft.com/scripting/debugging-powershell-script-in-visual-studio-code-part-2/

(5) obtain PowerShell-related content and commands

Using the shortcut key Ctrl+Shift+P in the panel, open the following quick command line and type powershell:

(VI) debugging tools

PowerShell Editor Services runs in a separate process and provides language and debugging services for Visual Studio Code through the JSON remote procedure call (RPC) protocol defined by Visual Studio Code. One advantage of this approach is that the crash of the PowerShell Editor Services process does not cause the Visual Studio code to crash. And, with the latest version of the PowerShell extension, you only need to restart the current PowerShell session without restarting the Visual Studio code to start over.

To open the Debug view, select Debug from the View menu in View Bar, or press Ctrl + Shift + D. In the Launch Configuration drop-down list (as shown in the screenshot below), select the PowerShell Launch (current file) configuration.

By default, debugging uses a launch.json file, as shown in the figure.

Breakpoints can be set before debugging and the problem can be determined by running the breakpoints line by line.

You can follow the official Wechat account below for more information.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.