Windows PowerShell Blog

Yeah!

You guys are the best!

Don't worry about us early adopters.  Who cares if you break my scripts... This isn't C# or VBScript it didn't take me that long to write them in the first place.  Given the current release cycle, Don't worry about us.  Just get it right!

By the time V2 is rolled out in production around the world (3-12 months after GA).  PowerShell will have reached a critical mass.  Like those who used monad before, the CTP crowd will be but a whisper...

As long as you get it right, who cares!  Feel free to break EVERYTHING with beta1.  If your road map says it's the right thing to do.  Part of what has made POSH so successful is your unorthodox approach to solving complex problems.  At this point "in powershell I trust", If you tell me that X is the best thing for everyone... I may not like it, but I'm not going back to cmd/wsh

~Glenn

PowerShell V2 Community Technology Preview 3 is public with lots of goodies. Read the announcement at

Just in time for Christmas, CTP3 of Powershell v2 was realeased last nigth and is available for download

Could we please for the love of all that is holy actually harmonize the releases between WinRM and PowerShell?  I mean, if PowerShell has a dependency on WinRM, and PowerShell CTP3 clearly supports XP, why the HELL can't I get WinRM CTP3 to support XP?????

FIX THIS!! This is the THIRD time you've done this since becoming dependent on WinRM and EACH time you've put out an update, you lock yourselves into Vista and Server 2008 ONLY even though your product SUPPORTS XP!!!!

Eric,

Feel your pain but there are alternatives for the time being.  nSofware has their Powershell Server which works in much the same way that WinRM does.  If your hair is on fire, as Jeffrey would say, go with what works now.

-Shane

The features discussed in this blog post depend on PowerShell CTP3 release. Details about PowerShell

Shane:  Thanks, and I get that I went overboard in my previous post, but it's not like this hasn't been discussed AND addressed before.  It's like all of Microsoft has been given the mantra "Do whatever it takes to PUSH customers off XP and to Vista."  

Unfortunately for folks like myself that prefer to keep up with the latest in tools and technology, we aren't always the final arbiter in what platforms we support, and continually having to lag behind everyone else to use something that is supported on XP (but one of it's dependencies prefers to support Vista...) is creating an increasingly bad taste in my mouth.  

I have Vista at home and use it to teach myself the skills I'll need to support it when the time comes, but there are LOTS of folks like myself who still support primarily 2000 and XP and have NO say in when that will change.

This is right up there with PS not working on 2k (because it does, it's strictly an installer limit in checking the O/S version)

PowerShell Team:  My apologies for my previous post's unwarranted vitriol.  It's the holidays and you guys/gals probably busted hump to get these bits out the door, and it IS appreciated!  My point was, this has been an on-going issue since deciding on WinRM as a dependency for remoting and I've brought the point up and had it addressed before in previous CTP bits for WinRM (they release only a .mui first, and then much later an .msi)

In any case, I'll be playing around with the new features (that I can) over the holidays and thanks again for this early Christmas present (even if I'm more the Grinch than Saint Nick!)

Merry Saturnalia!

Hi Do you think the release version will be available by mid March?

We are considering integrating PowerShell in a consumer product.

Thanks,

John.

The features discussed in this blog post depend on PowerShell CTP3 release. Details about PowerShell

The features discussed in this blog post depend on PowerShell CTP3 release. Details about PowerShell