VS Code with PowerShell extension - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to display the current date and time in PowerShell.

PowerShell

Get-Date | [1]

Drag options to blanks, or click blank then click option'

AGet-Content

BOut-File

CStart-Process

DWrite-Output

Attempts:

3 left

💡 Hint

Common Mistakes

Using Out-File writes to a file instead of showing output.

Using Start-Process starts a new process, not for output.

Using Get-Content reads from files, not for output.

The Write-Output cmdlet sends the output to the console, showing the current date and time.

2fill in blank

medium

Complete the code to list all running processes in PowerShell.

PowerShell

[1]

Drag options to blanks, or click blank then click option'

AGet-Process

BStart-Process

CGet-Service

DStop-Process

Attempts:

3 left

💡 Hint

Common Mistakes

Using Get-Service lists services, not processes.

Using Start-Process starts a new process, not lists them.

Using Stop-Process stops a process, not lists them.

Get-Process lists all running processes on your computer.

3fill in blank

hard

Fix the error in the code to read the content of a file named 'log.txt'.

PowerShell

Get-Content [1]

Drag options to blanks, or click blank then click option'

A-File log.txt

Blog.txt

C-Path log.txt

DPath log.txt

Attempts:

3 left

💡 Hint

Common Mistakes

Using -Path log.txt works but is not needed here.

Using -File log.txt is not a valid parameter.

Using Path log.txt causes syntax error.

You can pass the file name directly to Get-Content to read its content.

4fill in blank

hard

Fill both blanks to filter processes with CPU usage greater than 100.

PowerShell

Get-Process | Where-Object { $_.CPU [1] [2] }

Drag options to blanks, or click blank then click option'

A>

B100

C<

D50

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<' instead of '>' reverses the filter.

Using '50' instead of '100' changes the threshold.

The Where-Object filters processes where CPU is greater than 100.

5fill in blank

hard

Fill all three blanks to create a hashtable of process names and their IDs for processes using more than 50 CPU.

PowerShell

$result = @{}; foreach ($p in Get-Process | Where-Object { $_.CPU [3] 50 }) { $result[[1]] = [2] }

Drag options to blanks, or click blank then click option'

A$p.Name

B$p.Id

C>

D$p.CPU

Attempts:

3 left

💡 Hint

Common Mistakes

Using $p.Id as key and $p.Name as value swaps keys and values.

Using '<' instead of '>' changes the filter logic.

Using $p.CPU as key or value is incorrect.

This creates a hashtable where keys are process names and values are process IDs for processes with CPU usage greater than 50.

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