by Michael S. Kaplan, published on 2013/02/15 07:01 -05:00, original URI: http://blogs.msdn.com/b/michkap/archive/2013/02/15/10393862.aspx
This is going to be a quick follow-up to PowerShell ISE will do *everything* (IF YOU LET IT!).
Someone asked me how to use the PowerShell ISE in Windows 8.
Now everything I had done in prior blogs had usually been on Windows 7 or on Server 2008 R2, and I had never even thought about the Windows 8/Server 2012 story.
At the same time as luck would have it, someone at work had asked me to do something similar (I had been resistant since it seemed unneccesary to me at the time).
I figured I'd do a quick blog that could be reused for the other thing, too.
Easy, right?
Well, I have easy steps, right here!
To get the 64-bit legacy PowerShell on 64-bit Windows (or the 32-bit legacy PowerShell on 32-bit Windows), just run:
%windir%\System32\WindowsPowerShell\v1.0\powershell.exe
To get the 64-bit PowerShell ISE on 64-bit Windows (or the 32-bit PowerShell ISE on 32-bit Windows), just run:
%windir%\System32\WindowsPowerShell\v1.0\powershell_ise.exe
To get the 32-bit legacy PowerShell on on 64-bit Windows, just run:
%windir%\Syswow64\WindowsPowerShell\v1.0\powershell.exe
To get the 32-bit PowerShell ISE on 64 bit Windows, just run:
%windir%\Syswow64\WindowsPowerShell\v1.0\powershell_ise.exe
They work for every version of Windows that has PowerShell, in all languages -- programmatically, via Start|Run, via script, anywhere.
You can start it up or send it a cmdlet, whatever. :-)
Problem solved!
Each type of PowerShell has its one flaw, mind you.
The legacy PowerShell is using raster fonts,which should be changed to a TrueType/OpenType font like Consolas:
And the ISE is set to use Lucida Console by default; it too should be using Consolas in Tools|Options in the ISE:
And NOW we're done.
Now of course the people asking were mostly talking about doing it through the user interface.
Not an unreasonable request, and I'm not an unreasonable guy.
But it's gonna take some really serious explaining....
So for the full answer including the user interface piece, you will have to wait for Monday's blog! :-)
I suspect that in the end it will come out a bit less cheery than today's blog was....
Foreshaedowing: a sign of quality literature!
Maxwell J. Battcher on 15 Feb 2013 12:10 PM:
Typing the Win key and then the word PowerShell is easy enough. Also, Win+X and PowerShell is right there on that menu that pops up.
Michael S. Kaplan on 17 Feb 2013 8:58 AM:
Cool tricks I never knew about!
You must admit they aren't necessarily intuitive. plus, WHICH PowerShell did they start? (I assume it was the legacy one, using raster fonts!)
referenced by