http://blogs.msdn.com/powershell/archive/2008/12/24/windows-powershell-ctp2-to-ctp3-conversion-guide.aspxI write a lot of scripts, and, since I blog some of what I write, my home computer has been running Windows PowerShell CTP2 since it came out. Since CTP3 has a number of changes from CTP2, I've got to update my home script library to work with CTP3. Whileen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/powershell/archive/2008/12/24/windows-powershell-ctp2-to-ctp3-conversion-guide.aspx#9251368Wed, 24 Dec 2008 07:06:10 GMT91d46819-8472-40ad-a661-2c78acb4018c:9251368Oisin Grehan<p>Hey James! </p> <p>While poking around CTP3 in reflector, I noticed that there are type accelerators for runspace and runspacefactory: [runspace] and [runspacefactory] respectively. This would shorten your ctp3 version just a little bit more ;)</p> <p>- Ois</p>http://blogs.msdn.com/powershell/archive/2008/12/24/windows-powershell-ctp2-to-ctp3-conversion-guide.aspx#9251594Wed, 24 Dec 2008 11:46:19 GMT91d46819-8472-40ad-a661-2c78acb4018c:9251594PowerShellTeam<p>Thanks Oisin, I've updated the post.</p> <p>- James</p> http://blogs.msdn.com/powershell/archive/2008/12/24/windows-powershell-ctp2-to-ctp3-conversion-guide.aspx#9253868Sat, 27 Dec 2008 00:39:42 GMT91d46819-8472-40ad-a661-2c78acb4018c:9253868meanguy<p>&quot;Note that it's DefaultParameterSetName, not DefaultParameterSet. &nbsp;In my script collection, this was the most tedious thing to change out.&quot;</p> <p>Should've written a script to do it. &nbsp;:-)</p>http://blogs.msdn.com/powershell/archive/2008/12/24/windows-powershell-ctp2-to-ctp3-conversion-guide.aspx#9724210Wed, 10 Jun 2009 16:48:43 GMT91d46819-8472-40ad-a661-2c78acb4018c:9724210ivan<p>how comversion in downloads powershell ctp2 for ctp3 l would like make &nbsp;do</p>