RSSPDC 2008: Windows 7, WS2K8 R2 will get PowerShell v2
By Scott M. Fulton, III | Published October 30, 2008, 12:21 PM
At the early morning session on the final day of PDC 2008, architect Jeffrey Snover officially confirmed that Windows 7 and the R2 edition of Windows Server 2008 will both get version 2 of PowerShell as standard installation options.
In addition, Snover said, thanks to the ability for an upcoming version of the .NET Framework to run in systems without graphical overhead, PowerShell v2 will also be supported in Server Core, the streamlined, command-line-only installation option for Windows Server introduced with the 2008 edition. Server Core is typically meant for systems that do not need to be administered directly, and can instead use remote management tools.
Among the major new features being added to version 2 of PowerShell is extended support for remote management tools, including a variety of new cmdlets ("command-lets") for managing heterogeneous systems remotely. To demonstrate, Snover showed how cmdlets could retrieve information from a Linux-based virtual machine, all from a Windows-based command line.
But perhaps more importantly for the general user, every Windows 7 user will have access (at long last) to one of the most scriptable and adaptable command lines ever developed -- an extremely effective alternative to the DOS-like CMD.EXE. Version 2 will have, as we've reported before, a built-in script development environment that's independent of Visual Studio (and, as Snover clearly appreciates, independent of Notepad).
PowerShell cmdlets are actually implementations of .NET made very, very dynamic. Its purpose is to perform in-depth administrative tasks and monitor events and activities, though in version 1, the preferred language for writing new cmdlets and attaching them to the PS vernacular as snap-ins, has been C#. Starting with version 2, a user can conceivably write new PowerShell cmdlets in PowerShell, using the built-in IDE, completely independently of Visual Studio.
What that means is, every Windows 7 client will have the ability to have built for it a personalized, extensible management environment, with a checks-and-balances system that makes certain only authorized processes can make critical changes.
nice addition, goodbye to 'autoit' and maybe 'windows scripting host', but still not so impress considering their competitor already implementing something worthy to look at the OPENCL..gigaflops? lets imagine 1 cpu (multicore?)+2 gpu (nvidia sli cards) > supercomputer?.
btw: im a pc (windows + ubuntu on virtualbox), my latest pc core 2 quad, 4gb ram, geforce 9800, vista home premium so stop the trolling and assuming things. i love windows just dont like the future its heading.
ray ozzie (MS) said: Vista to me is the culmination of the old way of thinking as the desktop should be," he said, and the fact that it came out in 2007, as the industry was shifting from packaged software to Web-based applications, was "a huge disaster.
wtf are they thinking??
Score: 0
If they can effectively replace AutoIt, they've nailed a pretty large following right there.
Score: 0
Just imagine, scripting in Windows...
Now there is an innovation that's only 30 years behind the alternative environments...and excepting that UNIX IS a scripting language...
Score: 0
Thats funny, I've been scripting in Windows since it came out. Albeit, in many different forms. But hey, scripting is scripting.
Score: 0
"Scripting is scripting"
Yup, if no standards are employed...
Now that's funny!
Score: 0
It's automatically installed when installing SQL Server 2008 enterprise edition on XP and Vista
Score: 0
Not quite. That's Powershell 1.0
Score: 0