Microsoft launches PowerShell

This week at Microsoft's TechEd IT forum Microsoft's Bob Mugilia introduced a host of new Microsoft technologies.
One of the major announcements was that of PowerShell 1.0, a new command-line shell and scripting tool which lets IT managers control their Windows systems.

Formerly called "Monad", PowerShell is the first major update to the Windows command line since Windows NT 3.5 back in 1995. PowerShell can do things such as navigate through SQL tables as if they were directories on a computer.

Report a problem with article
Previous Story

The Battle For Middle-Earth II: Rise of the Witch-king Ships

Next Story

Windowblinds comes to Vista

33 Comments

Commenting is disabled on this article.

I don't see the point. Its a commandline, not a scripting language that can be run from the exisiting cmd.exe and has compatibility with many DOS games too!

sweet, that's ace, thank you very much!
using 2.00 dev version.

love how you can set different tabs up with different shells

This is really power user tool. But its not that hard to learn the basics. There is a getting started guide included with the install. As for the shell really has updated the command prompt window since maybe windows 95 and your right its awefull. Thank god there are several transulent command consoles that work with powershell.

function out-zip {
Param([string]$path)
$a=pwd
$path=$a.path+''+$path
if (-not $path.EndsWith('.zip')) {$path += '.zip'}

if (-not (test-path $path)) {
set-content $path ("PK" + [char]5 + [char]6 + ("$([char]0)" * 18))

}
$ZipFile = (new-object -com shell.application).NameSpace($path)
$input | foreach {$zipfile.CopyHere($_.fullname)}
}

To give you and idea of what can be done with powershell
Here is a simple script that outputs a contents of dir to a zip file.

Usage example:
dir *.txt | out-zip test.zip

Quote - Melfster said @ #7
Thank god there are several transulent command consoles that work with powershell.

Care to point out a few of these?

Quote - excalpius said @ #7.2
Or you could just open the file in WinRAR, do a File/Select All, then select Tools/Generate Report...ahem.

This could be used for servers who don't want to install 3rd party stuff or want to remotely admin the server through command line?


dir *.txt | out-zip test.zip

This is a good example. It shows how pipe don't pass text output, but a list of objects, that can always be mangled or worked with.

I truely like the idea.

Every unix had more powerfull shell than this one for ages (since the beginning to be clear, somewhere decennies ago)

It is really not a new thing,.... It is just copying unix (as they always did... they copy ideas of other)

Quote - tx83 said @ #7.5
Every unix had more powerfull shell than this one for ages (since the beginning to be clear, somewhere decennies ago)

It is really not a new thing,.... It is just copying unix (as they always did... they copy ideas of other)


wait a couple of years... and they'll say they have spent millions of $$$ in R&D on this... and Unix/Linux should pay them for using the idea..

Can anyone post a good guide for a n00b for monad? Is there anything a neophyte might want to try with it? or Is this only for the hardcore programmer?

when there was talk of the ui being 'not finalized' during the betas, I must admit I was hoping for at least something like 4nt or konsole rather , even xterm, rather than simply a blue console window.

I know the point of it is CLI but the odd gui bit (tabs when not fullscreen, better copy/paste control, full caret relocation with the mouse etc) are still damn useful and it's a real shame to have not had them optional.

screenshots not required. it's a command line utility. there is a steep learning curve but once you get the hang of it, it rocks.

It was a joke.

It is making fun of computer users who assume everything has a GUI, and ask for screenshots in forums of command line utilities.

If read properly, the /sorry should have been an indicator for sarcasm, or an apology for the lame joke.

Quote - K3vlar said @ #4.2
It was a joke.

It is making fun of computer users who assume everything has a GUI, and ask for screenshots in forums of command line utilities.

If read properly, the /sorry should have been an indicator for sarcasm, or an apology for the lame joke.


/sorry

That's pretty funny.

I'm thinking of other names used for shells.

There's bash
and ksh
and csh

I thought this used to be msh.

But psh?

Psh... Whatever.

Quote - semifamous said @ #3
That's pretty funny.

I'm thinking of other names used for shells.

There's bash
and ksh
and csh

I thought this used to be msh.

But psh?

Psh... Whatever.

Fail!

you are a bunch of idiot with no culture...

Bash : Bourne against Shell
Ksh : Korn Shell
Csh : C Sheel

Psh : PowerShell

Hasnt PowerShell (as in, the actual release version) been out for a while? I'm pretty sure its been on my computer for quite a few months.

Meh. Maybe this is just an update for it.

Quote - Rudy said @ #1
its a shame they didnt manage to include it in vista

It was never ment to be included. It's a developers tool.

Quote - Rudy said @ #1
its a shame they didnt manage to include it in vista

Expect to see it on the Longhorn server as it's meant to be a developers and admins tool instead of a client tool.

Quote - TheGriffin said @ #1.2

Expect to see it on the Longhorn server as it's meant to be a developers and admins tool instead of a client tool.

so should they take out the command prompt from vista too? im just saying it would have been a better shell instead of the command prompt (something windows has always lacked)

It's a developers tool.

It's mostly an administator's tool, so I also agree this is unfortunate. Windows XP Pro already provides plenty of new commands for administrators, so it's not a question of not providing the tools for those. But at least it's out now, in time for the RTM.

Quote - RealFduch said @ #1.5
Admins can easily get is.
I think MS didn't include it in Vista because they didn't want the pain of new wawe of script viruses.

No.

If you had worked with it, you'd know it will, by default, only run signed scripts. You can disable that, but I like the idea in general. Technically, you create a self-signing certificate, and sign your own local scripts with that.

So there is no way a .ps1 is going to run without my consent.

PowerShell is the only thing Microsoft has made in the past year that has gotten me excited. And this is coming from a Unix geek.