Pretty grid $colors = [enum]::GetValues([System.ConsoleColor]) Foreach ($bgcolor in $colors){ Foreach ($fgcolor in $colors) { Write-Host “$fgcolor|” -ForegroundColor $fgcolor -BackgroundColor $bgcolor -NoNewLine } Write-Host ” on $bgcolor” } Updated colours in newer powershell: https://gist.github.com/timabell/cc9ca76964b59b2a54e91bda3665499e
I’m not a fan of embedding my credentials into a script (which a few other example here do) and additionally, you generally can’t do this from something like Packer or some other system/configuration automation or in a cloud provider with an pseudo-randomly generated password. Plus, generally, I feel hardcoding your credentials into a script or … Read more
From Differences between the ISE and PowerShell console:- Limited support for interactive console apps, try cmd.exe, then try cmd.exe /k a) cmd.exe /c dir still works though, and more information is available here http://blogs.msdn.com/powershell/archive/2009/02/04/console-application-non-support-in-the-ise.aspx Console Application output is not colorful STA by default a) Try $host.Runspace.ApartmentState b) powershell is MTA by default (ApartmentState shows up … Read more
This worked for me: $postData = “žluťoučký kůň úpěl ďábelské ódy” Invoke-WebRequest -Uri ‘http://www.example.com/’ -Method Post -Body $postData -ContentType “text/plain; charset=utf-8” Adding the charset=utf-8 fixed my issue where the acute accent characters were getting converted to special symbols.
Suppose you want to write that in the same file, you can do as follows: Set-Content -Path “C:\temp\Newtext.txt” -Value (get-content -Path “c:\Temp\Newtext.txt” | Select-String -Pattern ‘H\|159’ -NotMatch)
Works for me. Parentheses make sure get-content is done before piping. Default depth of convertto-json is 2, which is often too low. function pjson ($jsonfile) { (get-content $jsonfile) | convertfrom-json | convertto-json -depth 100 | set-content $jsonfile }
Look closely at the two dashes in unzipRelease –Src ‘$ReleaseFile’ -Dst ‘$Destination’ This first one is not a normal dash but an en-dash (– in HTML). Replace that with the dash found before Dst.
Just to offer the alternative to the Test-Path cmdlet (since nobody mentioned it): [System.IO.File]::Exists($path) Does (almost) the same thing as Test-Path $path -PathType Leaf except no support for wildcard characters
Edit: Bernhard König reports in the comments that this has finally been fixed in Powershell 5. You are quite right. The -Wait option on Get-Content waits until the file has been closed before it reads more content. It is possible to demonstrate this in Powershell, but can be tricky to get right as loops such … Read more
There is a great article on TechNet from the Hey, Scripting Guy series that goes over a situation very similar to what you are describing: Renaming a computer and resuming the script after reboot. The magic is to use the new workflows that are part of version 3: workflow Rename-And-Reboot { param ([string]$Name) Rename-Computer -NewName … Read more