This site uses cookies for analytics, personalized content. By continuing to browse this site, you agree to this use. Learn More
Automating the world one-liner at a time…
February 23, 2015Feb 23, 201502/23/15[UPDATED] A newer, working version of the ISE Module Browser is now available on the PowerShell Gallery: https://www.powershellgallery.com/packages/ISEModuleBrowserAddon/
High quality reusable modules, like LEGO pieces, enable IT Pros to build automation solutions in minutes! Where can I find those high quality reusable modules?
June 27, 2012Jun 27, 201206/27/12This blog post applies to the Windows PowerShell Integrated Scripting Environment (ISE) in Windows 8 and Windows Server 2012. The ISE is also fully supported and available when Server 2012 is deployed using the Minimal Server Interface. To start ISE, type ise
June 12, 2012Jun 12, 201206/12/12This blog post applies to the Windows PowerShell Integrated Scripting Environment (ISE) in Windows 8 and Windows Server 2012. The ISE is also fully supported and available when Server 2012 is deployed using the Minimal Server Interface. To start ISE, type ise in a PowerShell console and press Enter
Very few things can be considered “cool” in an interactive command-line environment.
April 12, 2012Apr 12, 201204/12/12
Problem: Figuring out a cmdlet from its syntax can be overwhelming, especially for people new to PowerShell.
PS C:\> get-command get-process -syntax
Get-Process [[-Name] <string[]>] [-ComputerName <string[]>] [-Module] [-FileVersionInfo] [<CommonParameters>]
Get-Process -Id <int[]> [-ComputerName <string[]>] [-Module] [-FileVersionInfo] [<CommonParameters>]
Get-Process -InputObject <Process[]>
June 4, 2010Jun 4, 201006/4/10PowerShell ISE is a simple tool and in some cases it has the bare essentials. For instance, it does not have an option to save all files.
On the flipside, it offers an Object Model from its first version that allows adding features beyond the essentials like this one and many more.
July 13, 2009Jul 13, 200907/13/09Here is a collection of tips and tricks to debug PowerShell
Read UpThere is a 7-part series of “Debugging Monad Scripts” that Jon Newman wrote a few years ago that covers a lot of tips, including error handling, traps, tracing, and covers a lot of V1 stuff.
May 26, 2009May 26, 200905/26/09There were quite a few name changes in the ISE Object Model from CTP3 to RC
Using Update-TypeData, we can achieve some parity between the two
We can add aliases to the CTP3 version to make it look like the RC Version
For example,
April 21, 2009Apr 21, 200904/21/09Jeffry Snover and many other have used Start-Demo in powershell.exehttp://blogs.msdn.com/powershell/archive/2007/03/03/start-demo-help-doing-demos-using-powershell.aspx
Continuing the tradition, we now have ISEDemo.psm1
To use it, start ISE and runImport-Module ISEDemo.psm1 #(attached)Start-Demo c:\path\to\demofile.txt
Type enter to execute the command once its finished typing
You can escape to clear and type some other command
To get the next command again,
April 20, 2009Apr 20, 200904/20/09ISE has an F1 help feature, where if you press F1 when your caret is over a cmdlet name, context sensitive help opens.
Shay Levy has a nice post on F1 help in the ISE herehttp://blogs.microsoft.co.il/blogs/scriptfanatic/archive/2009/01/31/using-help-in-powershell-ise.aspxHe adds “I wanted to mimic the way ISE’s help works when you press F1 and allow an alias to be expanded to cmdlet name.” and he did it with calling hh.exe on the link
There is an alternative way;
April 17, 2009Apr 17, 200904/17/09Here is a collection of differences between the PowerShell_ise.exe and PowerShell.exe, as well as workaroundsand suggestion if you need them (assuming we have them :))
Limited support for interactive console apps, try cmd.exe, then try cmd.exe /k
cmd.exe /c dir still works though,
