Linked by Thom Holwerda on Thu 1st Nov 2007 20:24 UTC, submitted by Rahul
Thread beginning with comment 282489
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.





Member since:
2005-07-06
Not entirely. PowerShell, while built atop .NET, is still a new language. You can't just write C# (for example) at a prompt and expect it to work.
Because it's a .NET language, however, it can easily utilize .NET class libraries, or interop with COM/WMI/etc., for scenarios that the cmdlets alone don't yet cover. One difference from traditional shells is that there are no built-in commands.
WRT to the statement in the article:
While it's true that the default PowerShell host from MS is the standard console window, PowerShell implements command completion (and many other features) as functions which users may freely customize. There are currently several free and commercial shell hosts and custom functions that extend the default PowerShell environment with graphical shells and/or intellisense-like statement completion.
FYI, a CTP of PowerShell 2.0 will be released next week.
http://blogs.msdn.com/powershell/archive/2007/11/02/ctp-ctp-beta.as...