Platform-specific considerations in PowerShell - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a key platform-specific consideration when writing PowerShell scripts?

Different operating systems have different file paths, commands, and environment variables. PowerShell scripts must handle these differences to work correctly across platforms.

beginner

How does PowerShell handle file paths differently on Windows vs Linux?

Windows uses backslashes (\) in file paths, while Linux uses forward slashes (/). PowerShell provides automatic path conversion or you can use the Join-Path cmdlet to handle paths correctly.

intermediate

Why should you check the platform inside a PowerShell script?

To run platform-specific commands or adjust behavior, you can check the platform using the automatic variable $PSVersionTable.PSEdition or [System.Environment]::OSVersion.Platform.

intermediate

What is a common difference in environment variables between Windows and Linux in PowerShell scripts?

Windows environment variables are case-insensitive and accessed like $env:Path, while Linux variables are case-sensitive. Also, some variables exist only on one platform.

beginner

How can you write a PowerShell script that works on both Windows and Linux?

Use platform checks to run platform-specific code, use cmdlets like Join-Path for paths, avoid Windows-only commands, and test scripts on both platforms.

Which cmdlet helps handle file paths correctly across platforms in PowerShell?

A Set-Location

B Get-ChildItem

C New-Item

D Join-Path

Join-Path combines parts of a file path using the correct separator for the platform.

What symbol does Linux use for file paths that differs from Windows?

A /

B \

C :

D |

Linux uses forward slashes (/) in file paths, unlike Windows which uses backslashes (\).

How can you detect the operating system platform inside a PowerShell script?

A $PSVersionTable.PSEdition

B $env:OS

C Both A and D

D [System.Environment]::OSVersion.Platform

Both $PSVersionTable.PSEdition and [System.Environment]::OSVersion.Platform can be used to detect the platform.

Which environment variable behavior differs between Windows and Linux in PowerShell?

A Variable name prefix

B Case sensitivity

C Variable type

D Variable length

Windows environment variables are case-insensitive, while Linux environment variables are case-sensitive.

What is a good practice to make PowerShell scripts cross-platform?

A Use platform detection and platform-agnostic cmdlets

B Avoid platform checks

C Use Windows-only commands

D Hardcode file paths

Using platform detection and platform-agnostic cmdlets like Join-Path helps scripts run on multiple platforms.

Explain why platform-specific considerations are important when writing PowerShell scripts.

Think about how Windows and Linux handle files and commands differently.

Describe how you would write a PowerShell script that works on both Windows and Linux.

Consider how to handle differences in commands and file paths.

Practice

1. Which automatic variable in PowerShell helps you detect if the script is running on Windows?

easy

A. $IsLinux

B. $IsWindows

C. $IsMacOS

D. $Platform

Solution

1. Step 1: Understand platform detection variables

   PowerShell provides automatic variables like $IsWindows, $IsLinux, and $IsMacOS to detect the current OS.

2. Step 2: Identify the variable for Windows

   $IsWindows is true only when running on Windows, while others are for Linux or MacOS.

3. Final Answer:

   $IsWindows -> Option B

4. Quick Check:

   Windows detection = $IsWindows [OK]

Hint: Remember $IsWindows is true only on Windows systems [OK]

Common Mistakes:

• Confusing $IsLinux or $IsMacOS as Windows variables
• Using $Platform which does not exist
• Assuming $IsWindows works on Linux or Mac

2. Which of the following is the correct syntax to run platform-specific code only on Linux in PowerShell?

easy

A. if ($IsUnix) { Write-Host 'Running on Linux' }

B. if ($IsWindows) { Write-Host 'Running on Linux' }

C. if ($IsMacOS) { Write-Host 'Running on Linux' }

D. if ($IsLinux) { Write-Host 'Running on Linux' }

Solution

1. Step 1: Identify the variable for Linux

   $IsLinux is the automatic variable that is true only on Linux systems.

2. Step 2: Check the syntax for conditional execution

   The syntax if ($IsLinux) { ... } runs the block only on Linux.

3. Final Answer:

   if ($IsLinux) { Write-Host 'Running on Linux' } -> Option D

4. Quick Check:

   Linux code block = if ($IsLinux) [OK]

Hint: Use if ($IsLinux) for Linux-specific code blocks [OK]

Common Mistakes:

• Using $IsWindows or $IsMacOS for Linux code
• Using undefined variable $IsUnix
• Incorrect if statement syntax

3. What will be the output of this PowerShell script when run on macOS?

if ($IsWindows) { Write-Output 'Windows' } elseif ($IsLinux) { Write-Output 'Linux' } elseif ($IsMacOS) { Write-Output 'MacOS' } else { Write-Output 'Unknown' }

medium

A. MacOS

B. Linux

C. Windows

D. Unknown

Solution

1. Step 1: Understand the platform variables

   On macOS, $IsMacOS is true, while $IsWindows and $IsLinux are false.

2. Step 2: Follow the conditional logic

   The script checks $IsWindows (false), then $IsLinux (false), then $IsMacOS (true), so it outputs 'MacOS'.

3. Final Answer:

   MacOS -> Option A

4. Quick Check:

   macOS detection outputs 'MacOS' [OK]

Hint: Check $IsMacOS true for Mac output in if-elseif chain [OK]

Common Mistakes:

• Assuming Linux output on macOS
• Ignoring else block
• Confusing $IsWindows with $IsMacOS

4. You wrote this PowerShell script to run only on Windows:

if ($IsWindows) {
  Write-Output 'Windows detected'
} else {
  Write-Output 'Not Windows'
}

But it always outputs 'Not Windows' even on Windows. What is the likely problem?

medium

A. You ran the script in PowerShell Core on Windows but $IsWindows is true only in Windows PowerShell

B. You ran the script in PowerShell Core on Windows where $IsWindows is false

C. You ran the script in Windows PowerShell 5.1 on Windows where $IsWindows does not exist

D. You used $IsWindows without the $ sign

Solution

1. Step 1: Understand $IsWindows availability

   The $IsWindows automatic variable exists only in PowerShell Core 6.0+ and is true on Windows.

2. Step 2: Identify the likely problem

   In legacy Windows PowerShell 5.1, $IsWindows does not exist ($null/false), so the if condition fails even on Windows.

3. Final Answer:

   You ran the script in Windows PowerShell 5.1 on Windows where $IsWindows does not exist -> Option C

4. Quick Check:

   $IsWindows unavailable in PS 5.1 [OK]

Hint: Verify your PowerShell edition (powershell.exe vs pwsh.exe) [OK]

Common Mistakes:

• Forgetting $ sign on variable
• Assuming $IsWindows always true on Windows
• Confusing PowerShell Core and Windows PowerShell behavior

5. You want to write a PowerShell script that creates a folder named 'Logs' only on Windows and macOS, but skips Linux. Which code snippet correctly implements this platform-specific behavior?

hard

A. if ($IsWindows -or $IsMacOS) { New-Item -ItemType Directory -Path './Logs' }

B. if ($IsLinux) { New-Item -ItemType Directory -Path './Logs' }

C. if ($IsWindows -and $IsMacOS) { New-Item -ItemType Directory -Path './Logs' }

D. if ($IsUnix) { New-Item -ItemType Directory -Path './Logs' }

Solution

1. Step 1: Understand platform conditions

   You want to create the folder only on Windows or macOS, so the condition should check if either $IsWindows or $IsMacOS is true.

2. Step 2: Analyze each option

   if ($IsWindows -or $IsMacOS) { New-Item -ItemType Directory -Path './Logs' } uses -or to combine $IsWindows and $IsMacOS correctly. if ($IsLinux) { New-Item -ItemType Directory -Path './Logs' } creates folder only on Linux (wrong). if ($IsWindows -and $IsMacOS) { New-Item -ItemType Directory -Path './Logs' } uses -and which requires both true (impossible). if ($IsUnix) { New-Item -ItemType Directory -Path './Logs' } uses undefined $IsUnix which is falsey (wrong).

3. Final Answer:

   if ($IsWindows -or $IsMacOS) { New-Item -ItemType Directory -Path './Logs' } -> Option A

4. Quick Check:

   Use -or for Windows or Mac condition [OK]

Hint: Use -or to combine platform checks for multiple OS [OK]

Common Mistakes:

• Using -and instead of -or for multiple platforms
• Creating folder on Linux by mistake
• Using undefined variables like $IsUnix