Job Log

Powershell 4:Works well for Powershell 1 and 4:[Regex]::Split($builder.ToString(), [Environment]::NewLine)

need administrator privilege to do this.

Powershell profiles help us predefine variables/functions we use routinely and so we have them every time we launch Powershell. Also we can distribute profile to force powershell on all machines have

Powershell 32-bit and 64-bit version64-bit: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe32-bit: C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exealternative way

Below is the example:$scriptBlock = { param( [string]$name, [string]$gender, [int]$seconds ) Start-Sleep -Seconds $seconds; Echo "$name `t`t $gender" }$jobsList = @()$jobsList += Start-Job

This is the complete code:$p1 = [System.Diagnostics.Process]::Start("Powershell.exe", ".\Desktop\script1.ps1")$p2 = [System.Diagnostics.Process]::Start("Powershell.exe", ".\Desktop\script2.ps1")

[void] [System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms") try { $cmd = "Stop-Process -Name abc" Write-Warning "$cmd" In

Get-Content always automatically read in file text as string arrays. if we don't want that, we can use

$arr = New-Object int[] 3

Get-WmiObject Win32_Process -ComputerName localhost -Filter "Name like 'notepad%'" | Format-List -Property ProcessName, Path, CommandLine, WorkingSetSizeProcessName    : notepad.exePath    

It is actually part of ScriptCop http://scriptcop.start-automating.com/,

Unit Test framework:https://github.com/pester/PesterC:\PS>./bin/pester.batjust run pester.bat and all *.tests.ps1 will be

PS D:\> [char]0x00A5¥PS D:\> [char]0x00AE®PS D:\> [char]0x00AC¬PS D:\> [char]0x263a☺PS D:\> [char]0x263b☻PS D:\> [char]0x00E6æ

http://blogs.technet.com/b/heyscriptingguy/archive/2012/09/18/create-a-powershell-scheduled-job.aspx$dailyTrigger = New-JobTrigger -Daily -At "2:00 PM"$option = New-ScheduledJobOption -StartIfOnBat