VS Code with PowerShell extension - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this PowerShell command in VS Code terminal?

You run this command in the VS Code integrated terminal with PowerShell extension enabled:

Get-Process | Where-Object { $_.CPU -gt 100 }

What does this command output?

PowerShell

Get-Process | Where-Object { $_.CPU -gt 100 }

A A list of processes currently using more than 100 seconds of CPU time.

B An error saying 'CPU' property does not exist.

C All processes running on the system regardless of CPU usage.

D No output because the command is incomplete.

💡 Hint

Think about what the 'Where-Object' filter does with the CPU property.

The command lists all processes where the CPU time used is greater than 100 seconds. The 'CPU' property exists on process objects, so no error occurs.

📝 Syntax

intermediate

Which PowerShell script snippet correctly defines a function in VS Code with PowerShell extension?

You want to create a function named 'Get-Greeting' that returns 'Hello World'. Which snippet is correct?

A function Get-Greeting() => 'Hello World'

B def Get-Greeting() { 'Hello World' }

C func Get-Greeting { echo 'Hello World' }

D function Get-Greeting { return 'Hello World' }

💡 Hint

PowerShell functions use the keyword 'function' without parentheses for parameters if none.

Option D uses the correct PowerShell syntax for defining a function. Other options use syntax from other languages or invalid keywords.

🔧 Debug

advanced

Why does this PowerShell script fail to run in VS Code with PowerShell extension?

You wrote this script:

Write-Host "Starting script..." $number = 5 if $number -gt 3 { Write-Host "Number is greater than 3" }

When running, you get a syntax error. What is the cause?

PowerShell

Write-Host "Starting script..."
$number = 5
if $number -gt 3
{ Write-Host "Number is greater than 3" }

A Missing parentheses around the condition in the if statement.

B Using Write-Host instead of Write-Output causes error.

C Variable $number is not initialized properly.

D Curly braces {} are not allowed in PowerShell.

💡 Hint

PowerShell requires conditions in if statements to be enclosed in parentheses.

PowerShell syntax for if statements requires the condition to be inside parentheses, like: if ($number -gt 3) { ... }

🚀 Application

advanced

How to run a PowerShell script file in VS Code terminal with the PowerShell extension?

You have a script file named 'script.ps1' in your workspace. Which command runs this script correctly in the VS Code integrated terminal?

A run script.ps1

B .\script.ps1

C powershell script.ps1

D execute script.ps1

💡 Hint

In PowerShell, to run a script in the current directory, you prefix with .\

Option B correctly runs the script by specifying the relative path with .\. Other options are invalid commands.

🧠 Conceptual

expert

What is the purpose of the PowerShell extension in VS Code?

Select the best description of what the PowerShell extension adds to VS Code.

A It replaces the VS Code terminal with a custom PowerShell-only terminal.

B It converts PowerShell scripts into executable files automatically.

C It provides syntax highlighting, IntelliSense, debugging, and integrated terminal support for PowerShell scripts.

D It allows running PowerShell scripts only on Windows machines.

💡 Hint

Think about what features help you write and debug scripts inside VS Code.

The PowerShell extension enhances VS Code by adding editing features like syntax highlighting, code completion, debugging tools, and terminal integration for PowerShell.

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