CTP: Watch This Space

CTP: Watch This Space

  • Comments 31

Next week we'll be releasing a Community Technology Preview (CTP) of Windows PowerShell V2.0.

This release will not be for everyone.

This morning I wrote 3 blog entries that set your expectation about the CTP. I decided to blog them BEFORE the CTP because when you see what is in the CTP – most of you will make a mad rush to download it and use it. It has some amazingly cool stuff in it (you'll hear more about that next week). You really need to read and understand my 3 blogs before making the decision to participate in the CTP:

  1. CTP != Beta !
  2. Platform Requirements
  3. Versioning

One point is worth making again (and again): Things WILL change. If you are going to be disappointed or angry if we refactor our APIs or change our naming or tweak our semantics and break all your (CTP-specific) code/scripts – you should not use the CTP.

Bloggers – please do me a favor. If you pick up the CTP and start writing about it, please include a reference to this blog entry. Consider adding the words:

The PowerShell V2 CTP is not for everyone. You should read this PowerShell Team blog entry ( http://blogs.msdn.com/powershell/archive/2007/11/02/ctp-watch-this-space.aspx ) to find out what it is and what it isn't and then make an informed decision before installing the CTP.

I given lots of caution and caveats today but for those of you that participate in the CTP – I think you are going to be very pleased by what you see. Then again – if you aren't – you can tell us and there is a good chance that we'll be able to do something about it before we ship!

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

Leave a Comment
  • Please add 8 and 2 and type the answer here:
  • Post
  • 声明: The PowerShell V2 CTP is not for everyone. You should read this PowerShell Team blog entry ( http://blogs.msdn.com/powershell/archive/2007/11/02/ctp-watch-this-space.aspx

  • Using PowerLocker and the PowerShell v2 CTP to encrypt scripts, and output true .NET objects. ...

  • At the risk of sounding ignorant, I have a request.  I haven't yet found a way to run a script and have it close the PowerShell command window.  Perhaps I missed something, perhaps I'm not creative enough.

    I wrote a script  called "Done.ps1" that saves a command history, then give it an alias.  Then, instead of typing "Exit", I just type "Done" and my command history gets saved.

    Typing "Exit" in the command line works, but doesn't work in a script.  A simple command window exit would be nice.

  • When I open a PS v2 (CTP) session on my WinXP x64 box (.NET Framework v. 3.0), I get the following error listing:

    Error loading the extended type data file:

    Microsoft.Powershell.Core, C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml(259) : Error in type "System.DirectoryServices.DirectoryEntry": Exception: Cannot convert "Microsoft.PowerShell.AdapterCodeMethods" to "System.Type".

    Microsoft.Powershell.Core, C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml(266) : Error in type "System.DirectoryServices.DirectoryEntry": Exception: Cannot convert "Microsoft.PowerShell.AdapterCodeMethods" to "System.Type".

    Microsoft.Powershell.Core, C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml(277) : Error in type "System.IO.DirectoryInfo": Exception: Getter method should be public, non void, static, and have one parameter of type PSObject.

    Microsoft.Powershell.Core, C:\WINDOWS\SysWOW64\WindowsPowerShell\v1.0\types.ps1xml(308) : Error in type "System.IO.FileInfo": Exception: Getter method should be public, non void, static, and have one parameter of type PSObject.

    How can I take care of this?

    - Brian

  • I get the same error on Windows 2003

    PS P:\> Update-TypeData

    Update-TypeData : Error loading the extended type data file:

    Microsoft.PowerShell.Core, C:\WINDOWS\system32\WindowsPowerShell\v1.0\types.ps1xml(259) : Error in type "System.Directo

    ryServices.DirectoryEntry": Exception: Cannot convert "Microsoft.PowerShell.AdapterCodeMethods" to "System.Type".

    Microsoft.PowerShell.Core, C:\WINDOWS\system32\WindowsPowerShell\v1.0\types.ps1xml(266) : Error in type "System.Directo

    ryServices.DirectoryEntry": Exception: Cannot convert "Microsoft.PowerShell.AdapterCodeMethods" to "System.Type".

    Microsoft.PowerShell.Core, C:\WINDOWS\system32\WindowsPowerShell\v1.0\types.ps1xml(277) : Error in type "System.IO.Dire

    ctoryInfo": Exception: Getter method should be public, non void, static, and have one parameter of type PSObject.

    Microsoft.PowerShell.Core, C:\WINDOWS\system32\WindowsPowerShell\v1.0\types.ps1xml(308) : Error in type "System.IO.File

    Info": Exception: Getter method should be public, non void, static, and have one parameter of type PSObject.

    At line:1 char:15

    + Update-TypeData <<<<

  • I get same in Win XP SP2 x86

    Error loading the extended type data file:

    Microsoft.PowerShell.Core, C:\WINDOWS\system32\WindowsPowerShell\v1.0\types.ps1xml(259) : Error in type "System.DirectoryServices.

    DirectoryEntry": Exception: Cannot convert "Microsoft.PowerShell.AdapterCodeMethods" to "System.Type".

    Microsoft.PowerShell.Core, C:\WINDOWS\system32\WindowsPowerShell\v1.0\types.ps1xml(266) : Error in type "System.DirectoryServices.

    DirectoryEntry": Exception: Cannot convert "Microsoft.PowerShell.AdapterCodeMethods" to "System.Type".

    Microsoft.PowerShell.Core, C:\WINDOWS\system32\WindowsPowerShell\v1.0\types.ps1xml(277) : Error in type "System.IO.DirectoryInfo":

    Exception: Getter method should be public, non void, static, and have one parameter of type PSObject.

    Microsoft.PowerShell.Core, C:\WINDOWS\system32\WindowsPowerShell\v1.0\types.ps1xml(308) : Error in type "System.IO.FileInfo": Exce

    ption: Getter method should be public, non void, static, and have one parameter of type PSObject.

  • The PowerShell 2.0 CTP is nearly here!

  • For anyone receiving errors with the v2 CTP as indicated in the comments above, please email me directly marco DOT shaw AT gmail DOT com

    I would like to help troublshooting directly.

  • Has the issue with loading the type data been resolved?  I've just installed on a winXP box and am getting the same thing.

  • Could folks, who are running into this issue, specify the steps that causes this error? Is it while calling update-typedata with the custom types they defined or it is thowrs up while running some specific command?

    Hemant Mahawar

    Program Manager

    Windows PowerShell

  • opening Powershell creates these messages

  • opening powershell creates these errors/messages

  • I too am getting these errors on startup of Powershell on Windows XP x64

  • "Win XP SP3 x86

    Error loading the extended type data file:

    Microsoft.PowerShell.Core, C:\WINDOWS\system32\WindowsPowerShell\v1.0\types.ps1xml(259) : Error in type "System.DirectoryServices."

    I decided to uninstall and install PSv2. No improvements to the situation. :(

  • (Did I give it away by putting the &quot;1&quot; next to the CTP?) Well put your seatbelts on baby because

Page 2 of 3 (31 items) 123