Hey, Scripting Guy! How can I run a Windows PowerShell script from the Run dialog box or from a shortcut? In the Run dialog box I type something like c:\scripts\test.ps1 but my script just opens up in Notepad.
Hey, RS. We have just one thing to say: University of Washington 29, UCLA 19. And this after the Huskies trailed 16-0 late in the first half. Granted, it's still early, but at 3-1 the UW already has as many wins this year as they've had in the last two seasons combined.
But that’s all we’re going to say. After all, the Scripting Guy who writes this column knows enough about sports to know better than to jinx a team just when things are starting to look up. So let's just say that it's always nice to beat UCLA and leave it at that. See you all tomorrow!
Pardon? How can you run a Windows PowerShell script from the Run dialog box or from a shortcut? Um, didn't we tell you that we only had one thing to say? And we already said it: University of Washington 29, UCLA 19.
Could we put you on hold for a second? Really? You’re kidding, right? Wow; we wouldn’t have guessed that in a million years.
OK. Apparently, or at least from what we’ve been told, not everyone in the world is a college football fan. That’s hard for us to believe: people would rather know how to run a Windows PowerShell script from the Run dialog box or from a shortcut than talk about Saturday’s Husky-UW game? But, just in case, we’ll see if we can answer your question, RS.
No, no need to thank us; it’s no problem. Besides, we have a few hours to kill before the Husky Highlight show comes on anyway.
So why do your Windows PowerShell scripts keep opening up in Notepad? That’s because the Windows shell – bless its heart – doesn’t know what to do with Windows PowerShell scripts. The last time we installed Windows PowerShell (and remember, the application is still in beta, so the installation process might have changed since then) script files (files with a .ps1 file extension) were automatically associated with Notepad. That’s probably why your script files keep opening up in Notepad: ours do, too, simply because that’s what the Windows shell does with .ps1 files.
Of course, that might lead you to believe that all you have to do is associate .ps1 files with the Windows PowerShell executable file and everything will be hunky-dory. That’s what we thought, too, but that doesn’t seem to work. Instead, in order to start a Windows PowerShell script from the Run dialog box or from a shortcut (or, for that matter, from Cmd.exe) you need to explicitly start Windows PowerShell and then pass the path to the script file as a startup parameter. In other words, this command will start Windows PowerShell and run the script C:\Scripts\Test.ps1:
Of course, if you immediately ran off and tried that command, without bothering to read the rest of the column (for shame!) you were likely disappointed. “Wait a second; that doesn’t work, either,” you’re likely grumbling. “I saw a brief flash and then, nothing. Nice try, Scripting Guys, but no cigar!”
To tell you the truth, your command probably did work; the problem is that Windows PowerShell started, the script ran, the script finished, and then Windows PowerShell automatically terminated, just like that. You can verify that this is what’s happening by running a script that saves data to a text file. Start the script using the method outlined above, and then check to see if the text file was created and the data saved. If it was, then the command worked; it’s just that Windows PowerShell did its thing and then, like the Lone Ranger, disappeared before you could even thank it.
Now, that’s all fine and dandy … unless you need to read the output onscreen. In that case we have a problem, because everything typically happens way too fast for the human eye to follow. (Granted, the Scripting Editor insists that she can spot dangling participles and split infinitives even at that speed. But, remember, we said it was too fast for the human eye to follow.) If you need to read output onscreen what you have to do is tell Windows PowerShell to keep its command window open after the script finishes running. That’s something you can do by adding the –noexit parameter to your command:
powershell.exe –noexit c:\scripts\test.ps1
Give that a try and see what happens. When you do, make sure you leave –noexit as the first parameter. In our experience, switching the parameters around (that is, first specifying the script path and then tacking on –noexit) won’t work.
But, then again, you should always do everything exactly the way the Scripting Guys tell you.
OK, good point, even though the first explosion wasn’t entirely our fault; if dolphins are so smart then they should known better. But at least type your Windows PowerShell command exactly the way we told you.
We hope that solves your problem, RS. If you need more information about Windows PowerShell you might take a look at our Windows PowerShell center; among other things, you’ll find a new excerpt from the forthcoming book Windows PowerShell in Action, written by Microsoft’s own Bruce Payette. And stay tuned for Windows PowerShell Week, a series of five webcasts (aimed squarely at beginners) scheduled for November 6-10. We’ll have more information on Windows PowerShell Week very soon.
Most important of all, next week the Huskies travel to Arizona to play the Wildcats. Could the Huskies really start the season 4-1, including 2-0 in conference play? Let’s put it this way: if they do, it’s a pretty safe bet you’ll be able to read about it here. Will you also be able to read about scripting-related stuff here? In the immortal words of Bart Simpson, we can’t promise to try. But we promise to try to try.