http://blogs.msdn.com/powershell/archive/2008/12/23/advanced-functions-and-test-leapyear-ps1.aspxWelcome to CTP3! There are just an amazing amount of really important features in V2 but the one I want everyone to start using ASAP is Advanced Functions. In CTP2 we called this cmdlets. We dropped that term in favor of taking the idea of a FUNCTIONen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/powershell/archive/2008/12/23/advanced-functions-and-test-leapyear-ps1.aspx#9249453Tue, 23 Dec 2008 10:09:40 GMT91d46819-8472-40ad-a661-2c78acb4018c:9249453SPowser<p>One of my favorite parts of Cmdlets/Advanced Functions is the ParameterSets. &nbsp;These truly give a customized experience to the end user depending on what parameters they pass. &nbsp;I highly encourage people to explore those options as well.</p> <p>-Shane</p>http://blogs.msdn.com/powershell/archive/2008/12/23/advanced-functions-and-test-leapyear-ps1.aspx#9249993Tue, 23 Dec 2008 16:28:12 GMT91d46819-8472-40ad-a661-2c78acb4018c:9249993barlog<p>2008 年もあと少し。 今年も皆さんにはお世話になりました。 私事ですが来る新年も祖母が他界したため年始のご挨拶を控えさせて頂きます。 今後ともよろしくどうぞ...</p> http://blogs.msdn.com/powershell/archive/2008/12/23/advanced-functions-and-test-leapyear-ps1.aspx#9250559Tue, 23 Dec 2008 21:31:03 GMT91d46819-8472-40ad-a661-2c78acb4018c:9250559Chris Federico<p>Mr. Snover ..</p> <p>This is some awesome stuff Sir . Thank you for CTP 3 . Happy Holidays !!</p> <p>Chris</p>http://blogs.msdn.com/powershell/archive/2008/12/23/advanced-functions-and-test-leapyear-ps1.aspx#9251061Wed, 24 Dec 2008 01:39:32 GMT91d46819-8472-40ad-a661-2c78acb4018c:9251061Andy<p>Thanx !</p> <p>A Happy Christmas to the Team.</p>http://blogs.msdn.com/powershell/archive/2008/12/23/advanced-functions-and-test-leapyear-ps1.aspx#9251722Wed, 24 Dec 2008 15:02:42 GMT91d46819-8472-40ad-a661-2c78acb4018c:9251722tfl<p>I'm unclear on the use of the &quot;&lt;#&quot; and &quot;#&gt;&quot; lines.</p> <p>When I use them in my own scripts, they do work (no help info is produced. Removing them and the get-help returns help info.</p> <p>Also - putting in a #Requires -version 2.0 stops help from working.</p> <p>Is there some documentation on this feature?</p>http://blogs.msdn.com/powershell/archive/2008/12/23/advanced-functions-and-test-leapyear-ps1.aspx#9251726Wed, 24 Dec 2008 15:12:55 GMT91d46819-8472-40ad-a661-2c78acb4018c:9251726Alexander Riedel<p>Why must the parameter position be specified?</p> <p>Isn't the order of parameter definition an indicator for position and sufficient?</p> <p>What is the use case for having the position specifier?</p>http://blogs.msdn.com/powershell/archive/2008/12/23/advanced-functions-and-test-leapyear-ps1.aspx#9251957Wed, 24 Dec 2008 20:10:13 GMT91d46819-8472-40ad-a661-2c78acb4018c:9251957PowerShellTeam<p>@Tfl</p> <p>&quot;&lt;#&quot; and &quot;#&gt;&quot; are block comment characters. &nbsp;Everything between them is a comment.</p> <p>Please file a bug on the #Requires breaking help.</p> <p>jps</p> http://blogs.msdn.com/powershell/archive/2008/12/23/advanced-functions-and-test-leapyear-ps1.aspx#9251964Wed, 24 Dec 2008 20:20:59 GMT91d46819-8472-40ad-a661-2c78acb4018c:9251964PowerShellTeam<p>@alex</p> <p>Great point!</p> <p>The problem comes when you have multiple parametersets. &nbsp;That might be hard to have an obvious solution. &nbsp;That said, the whole point of making these FUNCTIONS was to provide a smooth glide path from simple to sophosticated. &nbsp;As such, we could do this for the vast majority of the functions which will only have a single parameterset.</p> <p>Please file this as a bug/suggestion (on <a rel="nofollow" target="_new" href="https://connect.microsoft.com">https://connect.microsoft.com</a>) &nbsp;- we are at a point where that is the only input we can consider acting on for this release. </p> <p>Thanks!</p> <p>jps</p> http://blogs.msdn.com/powershell/archive/2008/12/23/advanced-functions-and-test-leapyear-ps1.aspx#9257590Tue, 30 Dec 2008 23:48:53 GMT91d46819-8472-40ad-a661-2c78acb4018c:9257590Chris Federico<p>JPS ,</p> <p> I have a question why did you not start the function with Function Test-Leapyear {</p> <p>}</p> <p>I just noticed this .Is this because your using a process block ?</p> <p>I had created a similar function and encased it in a Function Get-whatever {} with the process block inside and it didn't work . Taking away the Function keyword like you have written it works fine . Just wanted to know why that was ?</p> <p>Chris</p>http://blogs.msdn.com/powershell/archive/2008/12/23/advanced-functions-and-test-leapyear-ps1.aspx#9257941Wed, 31 Dec 2008 05:21:11 GMT91d46819-8472-40ad-a661-2c78acb4018c:9257941PowerShellTeam<p>@Chris</p> <p>I put it into a file Test-Leapyear.ps1 and put it into my path. &nbsp;That way I can just type Test-Leapyear and PS will find it and invoke it. &nbsp;When you declare it a FUNCTION you have to DOT-SOURCE the file before you can invoke it. &nbsp;There are pros and cons to each approach. &nbsp;This wasn't a function I intend to use a lot and maximal performance doesn't matter so I decided to make it an external file.</p> <p>jps</p> http://blogs.msdn.com/powershell/archive/2008/12/23/advanced-functions-and-test-leapyear-ps1.aspx#9258550Wed, 31 Dec 2008 17:56:56 GMT91d46819-8472-40ad-a661-2c78acb4018c:9258550Jeremy Pack<p>#Requires -Version 2.0 </p> <p>Is this supported in V1.0 ie is there a way to get PS V1.0 throw an error if it runs a scritpt that needs V2.0 of PS?</p>http://blogs.msdn.com/powershell/archive/2008/12/23/advanced-functions-and-test-leapyear-ps1.aspx#9258581Wed, 31 Dec 2008 18:31:12 GMT91d46819-8472-40ad-a661-2c78acb4018c:9258581PowerShellTeam<p>&gt; Is this supported in V1.0 ie is there a way to get PS V1.0 throw an error if it runs a scritpt that needs V2.0 of PS?</p> <p>Absolutely.</p> <p>jps</p>