Why cross-platform extends reach in PowerShell - See It in Action

Why cross-platform extends reach

📖 Scenario: You work in a small company that wants to share a simple message with users on different computer systems. Some users have Windows, others have Mac or Linux. You want to write a script that works on all these systems to show the same message.

🎯 Goal: Create a PowerShell script that stores a message, sets a platform name, and then prints a combined message showing the platform and the message. This will demonstrate how cross-platform scripts can reach more users.

📋 What You'll Learn

Create a variable called message with the exact text: 'Hello from cross-platform script!'

Create a variable called platform with the exact text: 'Windows'

Use a variable called fullMessage to combine platform and message with a colon and space between

Print the fullMessage variable

💡 Why This Matters

🌍 Real World

Scripts that work on many computer systems help companies reach more users without rewriting code for each system.

💼 Career

Knowing how to write cross-platform scripts is useful for IT professionals, system administrators, and developers who support diverse environments.

1

Create the message variable

Create a variable called message and set it to the string 'Hello from cross-platform script!'

PowerShell

# Create the message variable
# Your code here

Hint

Use $message = 'Hello from cross-platform script!' to create the variable.

2

Set the platform variable

Create a variable called platform and set it to the string 'Windows'

PowerShell

$message = 'Hello from cross-platform script!'
# Create the platform variable
# Your code here

Hint

Use $platform = 'Windows' to create the platform variable.

3

Combine platform and message

Create a variable called fullMessage that combines platform and message with a colon and space between, like 'Windows: Hello from cross-platform script!'

PowerShell

$message = 'Hello from cross-platform script!'
$platform = 'Windows'
# Combine platform and message into fullMessage
# Your code here

Hint

Use double quotes and variables inside to combine strings: "$platform: $message"

4

Print the full message

Print the variable fullMessage to show the combined message

PowerShell

$message = 'Hello from cross-platform script!'
$platform = 'Windows'
$fullMessage = "$platform: $message"
# Print the fullMessage variable
# Your code here

Hint

Use Write-Output $fullMessage to print the message.

Practice

1. Why is writing cross-platform PowerShell scripts important?

easy

A. They only work on Windows systems

B. They can run on Windows, Linux, and macOS without changes

C. They require special hardware to run

D. They are slower than platform-specific scripts

Solution

1. Step 1: Understand cross-platform meaning

   Cross-platform means the script runs on multiple operating systems like Windows, Linux, and macOS.

2. Step 2: Identify the benefit of cross-platform scripts

   Scripts that run on many systems reach more users and environments without rewriting code.

3. Final Answer:

   They can run on Windows, Linux, and macOS without changes -> Option B

4. Quick Check:

   Cross-platform = Runs everywhere [OK]

Hint: Cross-platform means runs on many OS types [OK]

Common Mistakes:

• Thinking cross-platform means Windows only
• Assuming special hardware is needed
• Believing cross-platform scripts are slower

2. Which PowerShell command syntax is correct for checking the OS platform in a cross-platform script?

easy

A. if ($env:OS -eq 'Linux') { Write-Host 'Linux' }

B. if ($PSVersionTable.OS -eq 'Windows') { Write-Host 'Windows' }

C. if ($PSVersionTable.Platform -eq 'Unix') { Write-Host 'Linux or macOS' }

D. if ($Platform -eq 'Unix') { Write-Host 'Unix' }

Solution

1. Step 1: Identify correct property for OS platform

   $PSVersionTable.Platform is the standard way to check OS platform in PowerShell Core.

2. Step 2: Check syntax correctness

   if ($PSVersionTable.Platform -eq 'Unix') { Write-Host 'Linux or macOS' } uses correct syntax and property. Others use invalid or non-existent properties.

3. Final Answer:

   if ($PSVersionTable.Platform -eq 'Unix') { Write-Host 'Linux or macOS' } -> Option C

4. Quick Check:

   Use $PSVersionTable.Platform for OS check [OK]

Hint: Use $PSVersionTable.Platform to detect OS [OK]

Common Mistakes:

• Using $env:OS which is Windows-only
• Referencing non-existent $PSVersionTable.OS
• Using undefined variable $Platform

3. What will this PowerShell Core script output on a Linux system?

if ($PSVersionTable.Platform -eq 'Unix') { 'Cross-platform script running' } else { 'Windows script running' }

medium

A. Cross-platform script running

B. Windows script running

C. Error: Property not found

D. No output

Solution

1. Step 1: Understand $PSVersionTable.Platform on Linux

   On Linux, $PSVersionTable.Platform equals 'Unix'.

2. Step 2: Evaluate the if condition

   The condition is true, so the script outputs 'Cross-platform script running'.

3. Final Answer:

   Cross-platform script running -> Option A

4. Quick Check:

   Linux means Platform='Unix' => Output A [OK]

Hint: On Linux, Platform is 'Unix' so if condition is true [OK]

Common Mistakes:

• Assuming Platform is 'Linux' instead of 'Unix'
• Expecting Windows output on Linux
• Thinking script throws error

4. This script is intended to run on Windows and Linux but uses a Windows-only environment variable. What is the problem?

if ($env:OS -eq 'Windows_NT') { Write-Host 'Windows' } else { Write-Host 'Linux or macOS' }

medium

A. The else block syntax is incorrect

B. Missing parentheses around condition

C. Write-Host is not supported on Linux

D. Using $env:OS is Windows-only and undefined on Linux

Solution

1. Step 1: Check environment variable usage

   $env:OS is defined only on Windows, so on Linux it is empty or undefined.

2. Step 2: Understand the problem with $env:OS

   Because $env:OS is missing on Linux, the script relies on a Windows-specific variable, making it non-portable.

3. Final Answer:

   Using $env:OS is Windows-only and undefined on Linux -> Option D

4. Quick Check:

   $env:OS is Windows-only env var [OK]

Hint: Avoid Windows-only env vars for cross-platform scripts [OK]

Common Mistakes:

• Thinking Write-Host is unsupported on Linux
• Believing parentheses are required around if condition
• Assuming else syntax is wrong

5. You want to write a PowerShell script that lists files differently on Windows and Linux but works on both. Which approach best extends your script's reach?

hard

A. Use $PSVersionTable.Platform to detect OS and run platform-specific commands

B. Use Windows-only cmdlets and expect errors on Linux

C. Write separate scripts for each OS and run manually

D. Ignore OS differences and run same commands everywhere

Solution

1. Step 1: Identify cross-platform detection method

   Using $PSVersionTable.Platform lets the script detect OS at runtime.

2. Step 2: Apply platform-specific commands conditionally

   Run Windows commands if on Windows, Linux commands if on Unix, ensuring script works everywhere.

3. Final Answer:

   Use $PSVersionTable.Platform to detect OS and run platform-specific commands -> Option A

4. Quick Check:

   Detect OS, run matching commands = best cross-platform practice [OK]

Hint: Detect OS, then run matching commands for best reach [OK]

Common Mistakes:

• Using Windows-only commands without checks
• Writing separate scripts instead of one cross-platform script
• Ignoring OS differences causing failures