You guys are making this too hard. PowerShell handles this quite elegantly e.g.: > $str1 = $null > if ($str1) { ‘not empty’ } else { ’empty’ } empty > $str2 = ” > if ($str2) { ‘not empty’ } else { ’empty’ } empty > $str3 = ‘ ‘ > if ($str3) { ‘not … Read more
You are reinventing the wheel. Normal PowerShell scripts have parameters starting with -, like script.ps1 -server http://devserver Then you handle them in a param section (note that this must begin at the first non-commented line in your script). You can also assign default values to your params, read them from console if not available or … Read more
You can use a space followed by the grave accent (backtick): Get-ChildItem -Recurse ` -Filter *.jpg ` | Select LastWriteTime However, this is only ever necessary in such cases as shown above. Usually you get automatic line continuation when a command cannot syntactically be complete at that point. This includes starting a new pipeline element: … Read more
PowerShell 3+ # This is an automatic variable set to the current file’s/module’s directory $PSScriptRoot PowerShell 2 Prior to PowerShell 3, there was not a better way than querying the MyInvocation.MyCommand.Definition property for general scripts. I had the following line at the top of essentially every PowerShell script I had: $scriptPath = split-path -parent $MyInvocation.MyCommand.Definition
Write-Host “$($assoc.Id) – $($assoc.Name) – $($assoc.Owner)” See the Windows PowerShell Language Specification Version 3.0, p34, sub-expressions expansion.
If, some time during a PowerShell session, you need to see or to temporarily modify the PATH environment variable , you can type one of these commands: $env:Path # shows the actual content $env:Path=”C:\foo;” + $env:Path # attach to the beginning $env:Path += ‘;C:\foo’ # attach to the end
Prerequisites: You need to be able to run PowerShell as an administrator You need to set your PowerShell execution policy to a permissive value or be able to bypass it Steps: Launch Windows PowerShell as an Administrator, and wait for the PS> prompt to appear Navigate within PowerShell to the directory where the script lives: … Read more
In PowerShell V1 there’s only # to make the text after it a comment. # This is a comment in PowerShell In PowerShell V2 <# #> can be used for block comments and more specifically for help comments. #REQUIRES -Version 2.0 <# .SYNOPSIS A brief description of the function or script. This keyword can be … Read more
If you’re using Windows Server 2008 R2 then there is an x64 and x86 version of PowerShell both of which have to have their execution policies set. Did you set the execution policy on both hosts? As an Administrator, you can set the execution policy by typing this into your PowerShell window: Set-ExecutionPolicy RemoteSigned For … Read more
Use $PSVersionTable.PSVersion to determine the engine version. If the variable does not exist, it is safe to assume the engine is version 1.0. Note that $Host.Version and (Get-Host).Version are not reliable – they reflect the version of the host only, not the engine. PowerGUI, PowerShellPLUS, etc. are all hosting applications, and they will set the … Read more