Mensch gegen Maschine
25. Januar 2008
Archiv
Artikel Tagged ‘2001’
Für alle die ihn nicht verstanden haben: wiki(GlaDOS) 
Schlagworte
bastelbude bethesda bilder budenintern CCC comedy comics düsseldorf design diablo II em 2008 euro 2008 evonik fallout filme firefox frauen fussball games gedanken google hessen kino landtagswahl microsoft musik netznews open source party playstation 3 plugins politik privat ps3 software sonstiges spassig sylvester technik theme undefinierbar video vista windows wordpressEmpfehlungen:
- Free Photoshop Plug-ins Collection
- Script to create SCCM Site boundaries automatically
- Snowish - Over 500 PNG Icons
- The Four Stages of File Growth - Part 1
- PHP File Manager: Simple Directory Listing
- SCCM : Deploying the App-V 4.5 client
- Merry Christmas From PowerShell: The CodeDownloader Module
<p>One of the great benefits of PowerShell V2 Advanced Functions is the ease in which you can support parametersets. ParameterSets are, well, different SETS of valid parameters. For instance you can say: <br>Get-Process -id 0</p> <p>Get-Process -Name *ss</p> <p>Those are 2 different parametersets for the Get-Process cmdlet. Here is an example of how you would code parametersets using advanced functions:</p> <p><font color="#0000ff" size="2" face="Consolas">function test-param <br>{ <br>param( <br>[Parameter(<strong><font color="#ff8000" size="3">ParameterSetName="p1",</font></strong>Position=0)] <br>[DateTime] <br>$d, </font></p> <p><font color="#0000ff" size="2" face="Consolas">[Parameter(<font color="#ff8000" size="3"><strong>ParameterSetName="p2",</strong></font> Position=0)] <br>[int] <br>$i <br>) <br> switch (<font color="#ff8000" size="3"><strong>$PsCmdlet.ParameterSetName</strong></font>) <br> { <br> "p1" { Write-Host $d; break} <br> "p2" { Write-Host $i; break} <br> } <br>}</font></p> <p> </p> <p> </p> <p>Now the question becomes - which Parameterset is used? Let's experiment. Clearly you can specify which parameter you want and the right thing will happen:</p> <p> </p> <p><font color="#0000ff" size="2" face="Consolas">PS> test-param -d (get-Date) <br>12/23/2008 3:25:25 PM <br>PS> test-param -i 42 <br>42</font></p> <p> </p> <p> </p> <p>But what happens when it is ambiguous? Where this is where the magic of PowerShell kicks in. PowerShell uses the types of the input to determine which one you want. If you specified a DateTime you probably want the p1 parameterset and if you specified a INT you probably want the p2 parameterset.</p> <p><font color="#0000ff" size="2" face="Consolas">PS> test-param (get-Date) <br>12/23/2008 3:37:01 PM <br>PS> test-param 42 <br>42</font></p> <p> </p> <p> </p> <p>This almost always does exactly what you want but if it doesn't, you can always say what you want and you'll get it (it is just a mechanism to relieve you of work!).</p> <p><font color="#0000ff" size="2" face="Consolas">PS> test-param -d 42 <br>1/1/0001 12:00:00 AM</font></p> <p> </p> <p>(That is the DATETIME corresponding to 42 TICKs of the clock! Was that really what you wanted? :-) )</p> <p> </p> <p> </p> <p> </p> <p> </p> <p>So now comes the interesting part. What if the parametersets are ambiguous. Let's redo the script and make both parameters be STRINGs and then convert to DATETIME and INT in the script and see what happens.</p> <p><font color="#0000ff" size="2" face="Consolas">function test-param <br>{ <br>param( <br>[Parameter(ParameterSetName="p1",Position=0)] <br><strong><font color="#ff8000">[String] <br>$d,</font></strong> </font></p> <p><font color="#0000ff" size="2" face="Consolas">[Parameter(ParameterSetName="p2", Position=0)] <br><strong><font color="#ff8000">[String] <br></font></strong></font><font color="#0000ff" size="2" face="Consolas"><strong><font color="#ff8000">$i</font></strong> <br>) <br> switch ($PsCmdlet.ParameterSetName) <br> { <br> "p1" { Write-Host <strong><font color="#ff8000">([DateTime]$d);</font></strong> break} <br> "p2" { Write-Host <strong><font color="#ff8000">([INT]$i);</font></strong> break} <br> } <br>}</font></p> <p><font color="#0000ff" size="2" face="Consolas"></font></p> <p><font color="#0000ff" size="2" face="Consolas"></font></p> <p><font color="#0000ff" size="2" face="Consolas">PS> test-param -i "42" <br>42</font></p> <p><font color="#0000ff" size="2" face="Consolas">PS> test-param "42" <br><font color="#ff0000">test-param : Parameter set cannot be resolved using the specified named par <br>ameters. <br>At line:1 char:11 <br>+ test-param <<<< "42" <br> + CategoryInfo : InvalidArgument: (:) [test-param], Parameter <br> BindingException <br> + FullyQualifiedErrorId : AmbiguousParameterSet,test-param</font> </font></p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p>If you don't specify which one you want, it is ambiguous. But let's say that as the script author, you know that 9 out of 10 times people are going to want the p2 parameterset. Do you really want to make people type in the parametername every time just to get around this ambiguity? Wouldn't it be great if the PowerShell team thought about such a circumstance and give you a mechanism to specify which parameterset to pick if things were ambiguous?</p> <p>OH WAIT - they did!</p> <p><font color="#0000ff" size="2" face="Consolas">function test-param <br>{ <br><strong><font color="#ff8000" size="3">[CmdletBinding(DefaultParametersetName="p2")]</font></strong> <br>param( <br>[Parameter(ParameterSetName="p1",Position=0)] <br>[String] <br>$d, </font></p> <p><font color="#0000ff" size="2" face="Consolas">[Parameter(ParameterSetName="p2", Position=0)] <br>[String]$i <br>) <br> switch ($PsCmdlet.ParameterSetName) <br> { <br> "p1" { Write-Host ([DateTime]$d); break} <br> "p2" { Write-Host ([INT]$i); break} <br> } <br>}</font></p> <p><font color="#0000ff" size="2" face="Consolas"></font></p> <p><font color="#0000ff" size="2" face="Consolas">PS> test-param 42 <br>42</font></p> <p> </p> <p>Party on!</p> <p>Jeffrey Snover [MSFT] <br>Windows Management Partner Architect <br>Visit the Windows PowerShell Team blog at: <a href="http://blogs.msdn.com/PowerShell">http://blogs.msdn.com/PowerShell</a> <br>Visit the Windows PowerShell ScriptCenter at: <a href="http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx">http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx</a></p><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9251133" width="1" height="1"> PowerShellTeam tag:google.com,2005:reader/feed/http://blogs.msdn.com/powershell/rss.xml Windows PowerShell Blog PowerShell V2: ParameterSets- 100 Websites With Outstanding Artistic Design
- Get Some Interface Design Inspiration with Pattern Tap
Neueste Kommentare