by Michael S. Kaplan, published on 2013/02/20 07:01 -05:00, original URI: http://blogs.msdn.com/b/michkap/archive/2013/02/20/10395416.aspx
Prior parts in these series such as PowerShell ISE will do *everything* (though some assembly may be required!) and PowerShell ISE (or legacy) will do *everything* (and it's really easy to start!) and PowerShell ISE will do *everything* (IF YOU LET IT!) all have some things in common.
They are all relevant.
They are all useful.
This fourth part of the series is the veriform appendix, whose only reason for being is masochists who are so sure that Windows 8 is more intuitive that they laugh at those easy shotcuts, certain that the intuitive Windows 8 user interface will make it all easier.
This part is to knock the wind out of their sails a bit....
To start, we'll go back to Windows 7, which was pretty intuitive here:
See how all four options are right on the Start Menu?
Windows 8 got rid of that.
So if you search for PowerShell in apps, you do get one relevant hit:
Unfortunately, it lies when it shows that image.
It launches the legacy PowerShell.
The one with the default Raster Fonts setting that corrupts so well.
Crap. And other four letter words.
It turns out we have to go to the Control Panel (which means it won't work on ARM, or on the non-Pro Surface.
Sigh. And other four letter words.
At least we can find the Control Panel!
Cool! And other four letter words (not all four letter words are bad!()
We dig into the control panel a bit.
System and Security? That sounds good.
Let's try it:
There we go!
Administrative Tools!
That's where we hid the PowerShell treasures!
Just pick either PoweerShell ISE (try not to pay attention to the missing fourth option on the list -- since you aren't supposed to use it anyway!).
We made it!
To the Integrated scipting Environment!
Of course the ones who used those dreaded easy shortcuts got there days ago!
Plus I doubt your ever would have found it without my bread crumbs! :-)
metathinker on 20 Feb 2013 7:47 AM:
Here's one dreaded easy shortcut:
1. Press the Windows key to go to the Start screen
2. Swipe from right / move mouse to right corner and drag straight down or up
3. Choose Settings
4. Choose Tiles
5. Turn on Show Administrative Tools
Now Powershell ISE will show up on the Start screen, and you can search for it!
FM on 20 Feb 2013 8:00 AM:
> Plus I doubt your ever would have found it without my bread crumbs! :-)
Typing 'ise' in a powershell prompt opens the powershell ise. Also, anything you type after 'powershell' in metro start search will be executed by powershell. So tapping windows key, typing 'powershell ise', and hitting enter will open the powershell ise.
Michael S. Kaplan on 20 Feb 2013 11:13 AM:
But is it intuitive? :-)
gm2k on 20 Feb 2013 12:15 PM:
Well, pressing the windows key and typing ISE when I want to launch the ISE seems pretty intuitive to me.
Heath Stewart on 20 Feb 2013 2:08 PM:
If you're an avid PowerShell use (console or ISE), pin PowerShell to your taskbar. After you start it once, right-clicking (or hold on a touch device) will bring up a menu for running as admin, the console, or the ISE programs. I use this almost entirely in place of cmd so while I'm in the desktop Start+<1-based Index of where it's pined> (ex: Start+2 for me) fires it up.
Joshua on 22 Feb 2013 9:07 AM:
Windows ARM is as good as dead. The only thing that can save it now is to push out an update that fully unlocks the actual desktop, but Microsoft hasn't the guts.
Kwpolska on 23 Feb 2013 12:27 AM:
Control Panel should be available on Windows RT, because it is a stock Windows app, just like Explorer.
@Joshua: apps won’t run anyways, because they would need to be re-compiled for the ARM instruction set.
Simon Buchan on 24 Feb 2013 1:54 AM:
I'm not sure why you're convinced that powershell.exe is "Broken old crappy powershell" and powershell_ise.exe is "The new hotness awesomesauce powershell!" - while ISE may be more useful for powershell script development, surely you're running the damn things with powershell.exe, right? I mean the whole point of a scripting language is that you can make scripts with it, and those (at least, the ones you write) are most likely going to be run from some sort of console.
Frankly, it's not even a particularly bad experience to write powershell in your own editor of choice (I do like Sublime Text a *lot*), pasting in any snippets into a console that you want to test, or using the tab-completion or -? for discoverability - the fact that you don't get full international output is not great, but so long as it can write it to a file correctly, I'm fine with that.
Michael S. Kaplan on 24 Feb 2013 5:05 PM:
I like being able to see my text, as do most people who follow this Blog! :-)
Michael S. Kaplan on 24 Feb 2013 5:31 PM:
Though not necessarily this particular blog, if you know what I mean! :-)
Joshua on 24 Feb 2013 6:42 PM:
@Kwpolska: There are many apps with developers ready and waiting. Most of the stuff that did come across from Unix in the porting will compile for ARM run just fine as a Win32 ANSI application but a rewrite for Metro's just not going to happen.
Michael S. Kaplan on 24 Feb 2013 9:26 PM:
I have my own ARM/WoA passion project, which I'll talk about in the blog on Monday morning....