DemoForEachNext.vbs<\/B> script, this means that the following command is executed for each element in the array:<\/P>Wscript.Echo i\n<\/PRE>\nAs long as there are more elements in the collection or array, the statements inside the loop continue to execute for each element. When there are no more elements in the collection or array, the loop is exited and execution continues with statement following the Next<\/B> statement. This is seen in DemoForEachNext.vbs<\/B>:<\/P>\n
DemoForEachNext.vbs<\/B><\/P>ary = Array(1,2,3,4,5)\nFor Each i In ary\n WScript.Echo i\nNext\nWscript.echo “All done”\n<\/PRE>\nWhy, you may ask, spend so much time talking about the DemoForEachNext.vbs<\/B> script? This is because the script works exactly like the DemoForEach.ps1<\/B> script. In the DemoForEach.ps1<\/B> PowerShell script, you first create an array that contains the numbers 1 through 5 and store that array in the $ary<\/B> variable. This is seen here:<\/P>$ary = 1..5\n<\/PRE>\nThen you use the ForEach statement to walk through the array contained in the $ary<\/B> variable. Use the $i<\/B> variable to keep track of your progress through the array. Inside the script block (the curly brackets) you display the value of each variable. The DemoForEach.ps1<\/B> script is seen here:<\/P>\n
DemoForEach.ps1<\/B><\/P>$ary = 1..5\nForeach ($i in $ary)\n{\n $i\n}\n<\/PRE>\nThe cool thing about Windows PowerShell is that you can also use the ForEach<\/B> statement from inside the Windows PowerShell console:<\/P>PS C:\\> $ary = 1..5\nPS C:\\> foreach($i in $ary) { $i }\n1\n2\n3\n4\n5\n<\/PRE>\nThe ability to use the ForEach<\/B> statement from inside the Windows PowerShell console can give you excellent flexibility when you are working interactively. However, much of the work done at the Windows PowerShell console consists of using pipelining. When you are working with the pipeline, you can use the ForEach-Object<\/B> cmdlet. This cmdlet behaves in a similar manner to the ForEach<\/B> statement but is designed to handle pipelined input. The difference is that you do not have to use an intermediate variable to hold the contents of the array. You can create the array and send it across the pipeline. The other difference is that you do not have to create a variable for the enumerator. You use the $_<\/B> automatic variable (which represents the current item on the pipeline) instead. This is seen here:<\/P>PS C:\\> 1..5 | ForEach-Object { $_ }\n1\n2\n3\n4\n5<\/p>\n<\/PRE>\n
Suppose that you do not want to work with all the numbers in the array. This is the same thing as if one of the honu on the St. Anthony decides to head to the surface for a breath of fresh air. I could stay at the boat and continue with the next turtle or I could make a break from the ship and follow my friend. This is illustrated here:<\/P>
Foreach (honu in St. Anthony)\n{\n If (honu leaves) { Make a break from ship }\n Take picture without approaching too close or harassing the turtle\n}\n<\/PRE>\nThis syntax is really illustrated in this image, where the honu makes a break from the ship:<\/P>![\"Image](\"http:\/\/img.microsoft.com\/library\/media\/1033\/technet\/images\/scriptcenter\/qanda\/hsg\/2009\/may\/hey0505\/hsg-05-05-09-02.jpg\")
\n
<\/P>\n
In VBScript terms, leaving a For\u2026Each\u2026Loop<\/B> early is called an Exit For<\/B> statement. You have to use an If<\/B> statement to perform the evaluation of the condition. When the condition is met, you call Exit For<\/B>. In the DemoExitFor.vbs<\/B> script you use an inline If<\/B> statement to make this determination. The inline syntax is more efficient for these kinds of things than spreading the statement across three different lines. The key thing to remember about the inline If<\/B> statement is it does not conclude with the final End<\/B> If statement. The DemoExitFor.vbs<\/B> script is seen here:<\/P>\n
DemoExitFor.vbs<\/B><\/P>ary = Array(1,2,3,4,5)\nFor Each i In ary\n If i = 3 Then Exit For\n WScript.Echo i\nNext\nWScript.Echo “Statement following Next”\n<\/PRE>\nIn Windows PowerShell terms, you use the break<\/B> statement to leave the loop early. Inside the script block you use an If<\/B> statement to evaluate the value of the $i<\/B> variable. If it is equal to 3, you call the break<\/B> statement and leave the loop. This line of code is seen here:<\/P>if($i -eq 3) { break }\n<\/PRE>\nThe complete DemoBreakFor.ps1<\/B> script is seen here:<\/P>\n
DemoBreakFor.ps1<\/B><\/P>$ary = 1..5\nForEach($i in $ary)\n{\n if($i -eq 3) { break }\n $i\n}\n“Statement following foreach loop”\n<\/PRE>\nWhen the DemoBreakFor.ps1<\/B> script runs, it displays the numbers 1 and 2. Then it leaves the ForEach<\/B> loop and runs the line of code following the ForEach<\/B> loop:<\/P>1\n2\nStatement following foreach loop\n<\/PRE>\nIf you did not want to run the line of code after the loop statement, you would use the Exit<\/B> statement instead of the Break<\/B> statement. This is shown in the DemoExitFor.ps1<\/B> script:<\/P>\n
DemoExitFor.ps1<\/B><\/P>$ary = 1..5\nForEach($i in $ary)\n{\n if($i -eq 3) { exit }\n $i\n}\n“Statement following foreach loop”\n<\/PRE>\nWhen the DemoExitFor.ps1<\/B> script runs, the line of code following the For<\/B> loop never executes. This is because the Exit<\/B> statement ends the script. The results of running the DemoExit script<\/B> are shown here:<\/P>1\n2\n<\/PRE>\nYou could achieve the same thing in VBScript by using the Wscript.Quit<\/B> statement instead of Exit For<\/B>. As with the DemoExitFor.ps1<\/B> script, the DemoQ<\/B>u<\/B>itFor.vbs<\/B> script never comes to the line of code following the For\u2026Each\u2026Loop<\/B>. This is seen here:<\/P>\n
DemoQuitFor.vbs<\/B><\/P>ary = Array(1,2,3,4,5)\nFor Each i In ary\n If i = 3 Then WScript.Quit\n WScript.Echo i\nNext\nWScript.Echo “Statement following Next”\n<\/PRE>\nDS, as you can see, you do not have to know how many items are contained within your collection in order to walk through them. In addition, even though you did not ask, we have also looked at exiting a ForEach<\/B> statement when a condition is met. We hope that you have enjoyed this discussion. Join us tomorrow as we examine decision making. Until then, peace.<\/P>\n
<\/P>\n
Ed Wilson and Craig Liebendorfer, Scripting Guys<\/B><\/P><\/p>\n","protected":false},"excerpt":{"rendered":"
Hey, Scripting Guy! Your article yesterday was fairly interesting. The problem is that every time that you looped through something, you needed to basically know how many times that you would loop because you needed to be able to count it. Also your analogy about walking on the beach was somewhat dumb. This is because […]<\/p>\n","protected":false},"author":595,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[51,3,4,45],"class_list":["post-53823","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-getting-started","tag-scripting-guy","tag-scripting-techniques","tag-windows-powershell"],"acf":[],"blog_post_summary":"
Hey, Scripting Guy! Your article yesterday was fairly interesting. The problem is that every time that you looped through something, you needed to basically know how many times that you would loop because you needed to be able to count it. Also your analogy about walking on the beach was somewhat dumb. This is because […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/53823","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/595"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=53823"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/53823\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=53823"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=53823"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=53823"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"Hey,](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/q-for-powertip.jpg\" "\\"Hey,")
<\/H2>\n![\"Spacer\"](\"https:\/\/devblogs.microsoft.com\/scripting\/wp-content\/uploads\/sites\/29\/2019\/05\/spacer.gif\")
![\"Hey,](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/a-for-powertip.jpg\" "\\"Hey,")
\n![\"Image](\"http:\/\/img.microsoft.com\/library\/media\/1033\/technet\/images\/scriptcenter\/qanda\/hsg\/2009\/may\/hey0505\/hsg-05-05-09-01.jpg\")
\n