VS Code with PowerShell extension - Mini Project: Build & Apply

VS Code with PowerShell extension

📖 Scenario: You are learning how to use Visual Studio Code (VS Code) with the PowerShell extension to write and run PowerShell scripts easily. This project will guide you through creating a simple PowerShell script, configuring a variable, writing a loop to process data, and displaying the output in the VS Code terminal.

🎯 Goal: Build a PowerShell script that stores a list of server names, sets a threshold number, filters servers based on the threshold, and prints the filtered list in the VS Code terminal.

📋 What You'll Learn

Create a list of server names with their CPU usage percentages

Add a threshold variable to filter servers by CPU usage

Use a loop or comprehension to select servers exceeding the threshold

Print the filtered server names and their CPU usage

💡 Why This Matters

🌍 Real World

System administrators often monitor server performance using scripts. This project shows how to filter and display server CPU usage data using PowerShell in VS Code.

💼 Career

Knowing how to write and run PowerShell scripts in VS Code is essential for IT professionals managing Windows servers and automating tasks.

1

Create the initial server data

Create a variable called servers that holds a dictionary with these exact entries: 'ServerA' = 45, 'ServerB' = 70, 'ServerC' = 30, 'ServerD' = 85

PowerShell

# Create the servers dictionary with CPU usage percentages
# Your code here

Hint

Use @{} to create a dictionary in PowerShell. Separate entries with semicolons.

2

Add a CPU usage threshold

Create a variable called threshold and set it to 50

PowerShell

$servers = @{ 'ServerA' = 45; 'ServerB' = 70; 'ServerC' = 30; 'ServerD' = 85 }
# Create the threshold variable and set it to 50
# Your code here

Hint

Just assign the number 50 to a variable named threshold.

3

Filter servers exceeding the threshold

Create a variable called highUsageServers that contains only the servers from $servers where the CPU usage is greater than $threshold. Use a foreach loop with if condition to add matching servers to highUsageServers.

PowerShell

$servers = @{ 'ServerA' = 45; 'ServerB' = 70; 'ServerC' = 30; 'ServerD' = 85 }
$threshold = 50
# Create an empty dictionary called highUsageServers
# Use foreach to add servers with usage > threshold
# Your code here

Hint

Start with an empty dictionary @{}. Loop over $servers.Keys. Use if to check if usage is greater than $threshold. Add matching servers to $highUsageServers.

4

Display the filtered servers

Use a foreach loop to print each server name and its CPU usage from $highUsageServers in the format: ServerB: 70%

PowerShell

$servers = @{ 'ServerA' = 45; 'ServerB' = 70; 'ServerC' = 30; 'ServerD' = 85 }
$threshold = 50
$highUsageServers = @{}
foreach ($server in $servers.Keys) {
    if ($servers[$server] -gt $threshold) {
        $highUsageServers[$server] = $servers[$server]
    }
}
# Print each server and its CPU usage from highUsageServers
# Your code here

Hint

Loop over $highUsageServers.Keys. Use Write-Output with an f-string style to print the server name and usage with a percent sign.

Practice

1. What is the main benefit of using the PowerShell extension in VS Code?

easy

A. It provides syntax highlighting and debugging for PowerShell scripts.

B. It automatically converts PowerShell scripts to other languages.

C. It disables the integrated terminal in VS Code.

D. It removes the need to write any PowerShell commands.

Solution

1. Step 1: Understand VS Code PowerShell extension features

   The extension adds helpful features like syntax highlighting and debugging to make scripting easier.

2. Step 2: Evaluate each option

   Only It provides syntax highlighting and debugging for PowerShell scripts. correctly describes these benefits. Options A, B, and C are incorrect or false.

3. Final Answer:

   It provides syntax highlighting and debugging for PowerShell scripts. -> Option A

4. Quick Check:

   PowerShell extension features = syntax highlighting and debugging [OK]

Hint: Remember: PowerShell extension improves script editing and debugging [OK]

Common Mistakes:

• Thinking it converts scripts to other languages
• Believing it disables the terminal
• Assuming it removes the need to write commands

2. Which of the following is the correct way to run a PowerShell script file named script.ps1 inside VS Code terminal?

easy

A. Run-File script.ps1

B. Execute script.ps1

C. ./script.ps1

D. Start script.ps1

Solution

1. Step 1: Identify how to run scripts in PowerShell terminal

   PowerShell runs scripts by calling their path, usually with ./filename.ps1 if in current folder.

2. Step 2: Check each option

   Only ./script.ps1 uses the correct syntax ./script.ps1. Others are invalid commands.

3. Final Answer:

   ./script.ps1 -> Option C

4. Quick Check:

   Run script with ./filename.ps1 [OK]

Hint: Use ./ before script name to run in terminal [OK]

Common Mistakes:

• Using non-existent commands like Run-File or Execute
• Forgetting ./ before script name
• Typing Start instead of running script path

3. Given this PowerShell script opened in VS Code:

Write-Host "Hello, VS Code!"

What will be the output when you run it in the integrated terminal?

medium

A. Write-Host "Hello, VS Code!"

B. Hello, VS Code!

C. Error: Command not found

D. No output

Solution

1. Step 1: Understand Write-Host command

   Write-Host prints the text string directly to the console output.

2. Step 2: Predict output of the script

   The script prints exactly: Hello, VS Code! to the terminal.

3. Final Answer:

   Hello, VS Code! -> Option B

4. Quick Check:

   Write-Host outputs text = Hello, VS Code! [OK]

Hint: Write-Host prints text exactly to terminal [OK]

Common Mistakes:

• Thinking it prints the command itself
• Expecting an error for a valid command
• Assuming no output is shown

4. You wrote this script in VS Code with PowerShell extension:

Write-Host "Start"
Write-Host "End"

But when you run it, only "Start" appears and then it stops. What is the likely cause?

medium

A. The script has a syntax error stopping execution.

B. Write-Host only prints the first line.

C. The integrated terminal is not open.

D. You pressed Ctrl+C stopping the script after first line.

Solution

1. Step 1: Analyze script behavior

   The script has two Write-Host lines, both valid and should print Start then End.

2. Step 2: Consider why only first line prints

   If execution stops early, a manual interrupt like Ctrl+C is likely cause, not syntax or terminal issues.

3. Final Answer:

   You pressed Ctrl+C stopping the script after first line. -> Option D

4. Quick Check:

   Manual interrupt stops script early [OK]

Hint: Check if script was manually stopped (Ctrl+C) [OK]

Common Mistakes:

• Assuming syntax error without checking
• Thinking terminal closed stops partial output
• Believing Write-Host prints only first line

5. You want to debug a PowerShell script in VS Code using the PowerShell extension. Which steps correctly start debugging?

hard

A. Open the script, press F5, and use breakpoints to pause execution.

B. Run the script in external PowerShell console only, no debugging in VS Code.

C. Right-click script and select 'Convert to Debug Mode' before running.

D. Save the script as .psdebug file and run it.

Solution

1. Step 1: Understand debugging in VS Code PowerShell extension

   You open the script, set breakpoints, and press F5 to start debugging inside VS Code.

2. Step 2: Evaluate options

   Open the script, press F5, and use breakpoints to pause execution. correctly describes this process. Options B, C, and D describe invalid or non-existent steps.

3. Final Answer:

   Open the script, press F5, and use breakpoints to pause execution. -> Option A

4. Quick Check:

   Debug with F5 and breakpoints in VS Code [OK]

Hint: Press F5 in VS Code to start debugging PowerShell scripts [OK]

Common Mistakes:

• Thinking debugging requires external console
• Looking for 'Convert to Debug Mode' option
• Saving script with wrong extension for debugging