Posted By: Charles | Dec 3rd, 2008 @ 1:19 PM | 72,019 Views | 15 Comments
Welcome to another edition of Expert to Expert. Once again the venerable language master Erik Meijer leads the conversation. This time, we're lucky enough to have PowerShell creator and Partner Architect Jeffrey Snover. Jeffrey is really passionate about PowerShell and has worked hard to see that his .NET shell scripting technology ships in Windows 7 (it is on by default in Windows 7 and is used by administration components of the new OS). Erik is a big fan of PowerShell (especially since the code name of PowerShell was "Monad"Smiley) so we figured it would be useful to have Erik dig into the nitty gritty of PowerShell with Jeffrey and determine exactly what PowerShell is, how it's designed (and why), how it's used primarily (and secondarily) and finally how it will evolve. PowerShell is much more than a Windows-based shell scripting language and engine. But what, exactly, does this statement mean? Tune in. This is yet another great conversation between two stalwarts of the programming industry. Enjoy!
Rating:
4
0
First of all, powershell is awesome, and I use it as much as possible, though the three letters "C", "M", & "D" tend to keep hanging around, mostly due to muscle memory.

.Jeffrey talks about the next CTP (CTP3 I guess) in the video. When will we be able to download CTP3 for Vista? I can't wait to get my hands on it. Smiley

IIRC Jeffrey said at his PDC session that CTP3 would be available in the December/January timeframe.

chasedj
chasedj
Hello.

I totally have a professional crush on Jeffrey Snover.

JoshRoss
JoshRoss
A righteous infliction of retribution manifested by an appropriate agent.
Does anyone have a link to the PowerShell SDK, that works?  There is a lot of confusion on forms that deal with this matter.
I remember powershell in beta - thanks for the remind to redownload - I am Microsoft partner do i count to be in the channel 9?
I have two more bug-reports for you:

1. The powershell window won't resize like a normal window. The stone-aged buffer-aproach is a bug in 2008.
2. If I pipe some long output to the more function, and want to see the output line by line,, it clutters the output with it's own promt for every line. That would have been a bug 50 years ago Wink

The best would be if these bugs could be worked around, or that I simply har missed something to make these things work Smiley
Microsoft Communities