In my earlier blog, I mentioned that we had changed things since the previous CTP. Rather than leave everyone wondering whether they were doomed or not, I decided to have an early release of that portion of the release notes. Here they are:
Breaking Changes to Windows PowerShell 1.0
1. The value of the PowerShellVersion registry entry in HKLM\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine has been changed to 2.0.
2. Added new language keywords: Data, Cmdlet, and DynamicParam. Any commands called data, cmdlet or dynamicParam are interpreted as language keywords and result in parsing errors.
3. Changes in argument separator behavior. In Windows PowerShell 1.0, $a.method(,1) is interpreted as a call with an array of 1 element, but $a.method(1,,2) generates a parsing error. In Windows PowerShell V2, both formats generate parsing errors.
4. New cmdlets and variables have been added. These are listed below. These new elements might conflict with variables and functions in profiles and scripts.
Breaking Changes to Windows PowerShell V2 (CTP)
Enjoy!
Jeffrey Snover [MSFT] Windows Management Partner Architect Visit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShell Visit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx