Automating the world one-liner at a time…
Next week we'll be releasing a Community Technology Preview (CTP) of Windows PowerShell V2.0. I'm going to hold off saying what is in it until next week. The purpose of this email is to set your expectations about the CTP.
Jeffrey Snover [MSFT]Windows Management Partner ArchitectVisit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShellVisit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx
Next week we'll be releasing a Community Technology Preview (CTP) of Windows PowerShell V2.0. This release
Next week we'll be releasing a Community Technology Preview (CTP) of Windows PowerShell V2.0. This
#REQUIRES? Please tell me you're kidding. You're not actually using the comment character for a, uhm, precompiler directive, right?
Shouldn't it be another weird language-level feature, like ... param?
What I mean is: please, can it not be a comment that's not a comment?
Wow. Just tried it. I see that #Requires is actually already in v1 so I guess my please is too late :-/
More about the very cool Powershell V2 CTP next week when my NDA expires, but before that a warning on
Having to uninstall V1.0 first is a poor user experience. I don't remember how, off hand, the downlevel installs were deployed (MSI or OCM) but MSI major upgrades can uninstall automatically with the right entries in the Upgrade table and scheduling the RemoveExistingProducts action. Major upgrades like this are trivial with a low test cost and beneficial to users' time.
CBS should be able to remove old files during the installation of the new version.
The Windows PowerShell Team is pleased to release the first Community Technology Preview (CTP) of Windows
The first CTP of Microsoft Powershell 2.0 is out! It doesn´t work very well with Vista RTM, so install
Sigh... PowerShell just gets messier and messier.
Why are we using .ps1 when the language is ps2?
Why are you waiting for external influence (CLR/BCL changes) to switch the file extension?
Requiring #requires at the top of a file does the exact same thing as having a different file extension anyway -- only it's messier, users don't know until they actually open the file, and it might get borked if someone wrote a comment like "#requires administrator access".
Even something like ".ps2.ps1" would be a better file extension, if you _really_ insist on keeping that utterly ridiculous "fail-in-some-way-at-some-time" compatibility with PS1.
Som jag skrev i mitt tidigare inlägg om PowerShell 2.0 (CTP) så går det alltså att ladda hem denna förhandstitt
The PowerShell team released a Community Technology Preview of PowerShell 2.0 this week. They have had
The PowerShell 2.0 CTP is nearly here!