PowerShell: shell scripting done right

by Devin Ganger

I've long been a shell scripter. My first introduction to scripting was constructing the 3,000+ lines of hand-written batch files that controlled the operation of my DOS-based BBS. Since I was active in several networks, I had a lot of utilities I had to cobble together, and batch files were the only way to do it.

Unfortunately, shell scripting under DOS and later Windows was always somewhat of a pain. Windows 2000, XP, and 2003 made some strides in making more and of the operating system accessible from the command line (and thus from shell scripts), but I'd really hit my stride in scripting under ksh (the Korn shell) in UNIX. If I really needed to do serious scripting on a modern Windows system, my choices were to either break out some other language such as VBScript or Python (maybe, under duress, JavaScript or Perl) or install Services for UNIX to get a real Korn shell.

Well, no more. Now I'm installing PowerShell, and I'm finding I can do some amazing things in a small amount of scripting. Take a look at this specific example I outline on my blog and tell me what you think.

PowerShell, though it's not yet RTM, is a powerful enough shell that I've found myself wishing that Microsoft would stop ignoring UNIX and actually port it to UNIX machines. PowerShell's innovations are clear enough to be of great value even on a UNIX system.

3 Comments


2006-06-15 05:29:13
Perhaps you could spare a sentence to mention what powershell is and add one of those url linky things to it.

2006-06-22 05:45:45
is this all?

2006-06-22 07:29:28
"This specific example" must have been the one that stayed home...



.Text - Application Error!
Details


Value cannot be null. Parameter name: value


Return to site