{"id":544,"date":"2010-01-11T14:33:52","date_gmt":"2010-01-11T19:33:52","guid":{"rendered":"http:\/\/jdhitsolutions.com\/blog\/2010\/01\/potential-pipeline-pitfall\/"},"modified":"2010-01-11T14:33:52","modified_gmt":"2010-01-11T19:33:52","slug":"potential-pipeline-pitfall","status":"publish","type":"post","link":"https:\/\/jdhitsolutions.com\/blog\/powershell\/544\/potential-pipeline-pitfall\/","title":{"rendered":"Potential Pipeline Pitfall"},"content":{"rendered":"

Last week I was helping someone out in the PowerShell forum at ScriptingAnswers.com<\/a>. The specific problem is irrelevant;l however I  learned something in the process that will affect how I write my own PowerShell functions from now on. Not being a developer I never picked up on this subtle (at least to me) distinction. Here\u2019s the deal.<\/p>\n

<\/p>\n

I suggested a solution to the original problem that would require two functions. My initial thought was to write a PowerShell expression that would take the results of the first function and pipe them to the second function. Since I wanted the second function to accept pipelined input, I wrote it with a Begin, Process and End script blocks.<\/p>\n

\n
\n
Function Sample {<\/pre>\n
<\/p>\n
 <\/pre>\n
<\/p>\n
    BEGIN {<\/pre>\n
<\/p>\n
     #code runs once before any pipelined objects are processed<\/span><\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
    PROCESS {   <\/pre>\n
<\/p>\n
     #code runs for each pipelined object, $_<\/span><\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
 <\/pre>\n
<\/p>\n
    END {<\/pre>\n
<\/p>\n
     #code runs once after every object has been processed<\/span><\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
} #end<\/span> function<\/pre>\n
<\/div>\n<\/div>\n
The BEGIN and END script blocks are optional, but I actually wanted to use the BEGIN script block to test a condition.  If the condition failed then I wanted the function to abort. Here\u2019s what I thought I could do:<\/p>\n
PS C:\\> functionA | functionB \u2013myParam foo<\/font><\/p>\n
In my mind, functionA would run and then the results would be passed to functionB. If the parameter test failed, according the code in my begin script block, then the second function would display an error and stop. But that is not what happened. I put in some debug messages and it looked like the second function was starting before the first!  Here are some sample functions that demonstrate this behavior.<\/p>\n
\n
\n
function<\/span> Do-A {<\/pre>\n
<\/p>\n
    write-host "Starting A"<\/span> -fore green<\/pre>\n
<\/p>\n
    <\/pre>\n
<\/p>\n
    for<\/span> ($i=1;$i-le 5;$i++) {<\/pre>\n
<\/p>\n
     $i<\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
    write-host "Ending A"<\/span>-fore Green<\/pre>\n
<\/p>\n
} #end A<\/span><\/pre>\n
<\/p>\n
 <\/pre>\n
<\/p>\n
Function Do-B {<\/pre>\n
<\/p>\n
 <\/pre>\n
<\/p>\n
    Begin {<\/pre>\n
<\/p>\n
        write-host "Starting B"<\/span> -fore Magenta<\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
    Process {<\/pre>\n
<\/p>\n
        $_*2<\/pre>\n
<\/p>\n
        sleep -mill 100    <\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
    End {<\/pre>\n
<\/p>\n
        write-host "Ending B"<\/span> -fore Magenta<\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
} #end B<\/span><\/pre>\n
<\/div>\n<\/div>\n
I expect the numbers 1-5 to be piped to the second function and multiplied by 2.<\/p>\n
PS C:\\> Do-A | Do-B<\/font><\/p>\n
Starting B<\/font> <\/p>\n
<\/font>Starting A
\n      
<\/font>2 <\/p>\n
4 <\/p>\n
6 <\/p>\n
8 <\/p>\n
10 <\/p>\n
Ending A<\/font> <\/p>\n
Ending B<\/font><\/font><\/p>\n
I get the results ok, but notice that I get the message from the Begin block in the second function first. This means that code like this will also not work as expected.<\/p>\n
\n
\n
Function Do-A {<\/pre>\n
<\/p>\n
    write-host "Starting A"<\/span> -fore green<\/pre>\n
<\/p>\n
 <\/pre>\n
<\/p>\n
    for<\/span> ($i=1;$i-le 5;$i++) {<\/pre>\n
<\/p>\n
     $i<\/pre>\n
<\/p>\n
    }    <\/pre>\n
<\/p>\n
    write-host "Ending A"<\/span>-fore Green<\/pre>\n
<\/p>\n
} #end A<\/span><\/pre>\n
<\/p>\n
 <\/pre>\n
<\/p>\n
Function Do-B {<\/pre>\n
<\/p>\n
 Param([switch<\/span>]$bail)<\/pre>\n
<\/p>\n
    Begin {<\/pre>\n
<\/p>\n
        write-host "Starting B"<\/span> -fore Magenta<\/pre>\n
<\/p>\n
            if<\/span> ($bail) {<\/pre>\n
<\/p>\n
                write-warning "Bailing"<\/span><\/pre>\n
<\/p>\n
                return<\/span><\/pre>\n
<\/p>\n
        }<\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
    Process {<\/pre>\n
<\/p>\n
        $_*2<\/pre>\n
<\/p>\n
        sleep -mill 100<\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
 <\/pre>\n
<\/p>\n
    End {<\/pre>\n
<\/p>\n
        write-host "Ending B"<\/span> -fore Magenta<\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
} #end B<\/span><\/pre>\n
<\/div>\n<\/div>\n
PS C:\\> Do-A | Do-B<\/font><\/p>\n
Starting B
\n      
<\/font><\/font>WARNING: Bailing<\/font> <\/p>\n
<\/font>Starting A
\n      
<\/font>2 <\/p>\n
4 <\/p>\n
6 <\/p>\n
8 <\/p>\n
10 <\/p>\n
Ending A<\/font> <\/p>\n
Ending B<\/font><\/font><\/p>\n
The reason for this behavior I learned is that in a pipelined expression, the Begin scriptblocks are all processed first. In my situation, only the second function had a Begin  script block so it was executed first. This makes sense and now that I understand that behavior I can code accordingly.<\/p>\n
\n
\n
function<\/span> Do-A {<\/pre>\n
<\/p>\n
    write-host "Starting A"<\/span> -fore green<\/pre>\n
<\/p>\n
 <\/pre>\n
<\/p>\n
    for<\/span> ($i=1;$i-le 5;$i++) {<\/pre>\n
<\/p>\n
     $i    <\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
    write-host "Ending A"<\/span>-fore Green<\/pre>\n
<\/p>\n
} #end A<\/span><\/pre>\n
<\/p>\n
 <\/pre>\n
<\/p>\n
Function Do-B {<\/pre>\n
<\/p>\n
 Param([switch<\/span>]$bail)<\/pre>\n
<\/p>\n
    Begin {<\/pre>\n
<\/p>\n
       write-host "Starting B"<\/span> -fore Magen        <\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
    Process {<\/pre>\n
<\/p>\n
        if<\/span> ($bail) {<\/pre>\n
<\/p>\n
                write-warning "Bailing"<\/span><\/pre>\n
<\/p>\n
                return<\/span><\/pre>\n
<\/p>\n
      }<\/pre>\n
<\/p>\n
        $_*2<\/pre>\n
<\/p>\n
        sleep -mill 100<\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
    End {<\/pre>\n
<\/p>\n
        write-host "Ending B"<\/span> -fore Magenta<\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
} #end<\/span> B<\/pre>\n
<\/div>\n<\/div>\n
Now if I pipe the functions, I get my desired effect.<\/p>\n
PS C:\\> Do-A | Do-B -bail<\/font><\/p>\n
Starting B<\/font><\/font>
\n    
<\/font>Starting A
\n      
<\/font>WARNING: Bailing
\n        
WARNING: Bailing
\n            
<\/font><\/font><\/font><\/font><\/font>WARNING: Bailing
\n      
WARNING: Bailing<\/font><\/font> <\/p>\n
WARNING: Bailing
\n          
<\/font><\/font><\/font><\/font>Ending A<\/font> <\/p>\n
Ending B<\/font><\/font><\/p>\n
My examples are overly broad and the point I want to emphasize is that in a pipelined expression all the Begin script blocks are executed first. This is not necessarily a bad thing, merely behavior you have to understand. As an admin I had a different expectation as to PowerShell\u2019s behavior.<\/p>\n
Here\u2019s one more example with yet another function thrown in.<\/p>\n
\n
\n
Function Foo-A {<\/pre>\n
<\/p>\n
 <\/pre>\n
<\/p>\n
    Write-Host "Starting Foo-A"<\/span> -ForegroundColor green<\/pre>\n
<\/p>\n
    dir $env:temp | where {$_.lastwritetime -gt<\/span> (Get-Date).AddDays(-1)}<\/pre>\n
<\/p>\n
    Write-Host "Ending Foo-A"<\/span> -ForegroundColor green<\/pre>\n
<\/p>\n
    <\/pre>\n
<\/p>\n
} #end A<\/span><\/pre>\n
<\/p>\n
 <\/pre>\n
<\/p>\n
Function Foo-B {<\/pre>\n
<\/p>\n
 <\/pre>\n
<\/p>\n
    begin<\/span> {<\/pre>\n
<\/p>\n
    <\/pre>\n
<\/p>\n
    Write-Host "Starting Foo-B"<\/span> -ForegroundColor magenta<\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
    <\/pre>\n
<\/p>\n
    process<\/span> {<\/pre>\n
<\/p>\n
     # write ("{0}  {1}  {2}" -f $_.fullname,$_.LastWriteTime,$_.length)<\/span><\/pre>\n
<\/p>\n
      Remove-Item $_.fullname -recurse -whatif<\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
    <\/pre>\n
<\/p>\n
    end<\/span> {<\/pre>\n
<\/p>\n
        Write-Host "ending Foo-B"<\/span> -ForegroundColor magenta<\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
 <\/pre>\n
<\/p>\n
} #end B<\/span><\/pre>\n
<\/p>\n
 <\/pre>\n
<\/p>\n
Function Foo-C {<\/pre>\n
<\/p>\n
 <\/pre>\n
<\/p>\n
    Begin {<\/pre>\n
<\/p>\n
    Write-Host "Starting Foo-C"<\/span> -ForegroundColor Cyan<\/pre>\n
<\/p>\n
     } <\/pre>\n
<\/p>\n
    <\/pre>\n
<\/p>\n
    Process {<\/pre>\n
<\/p>\n
      #not really doing anything<\/span><\/pre>\n
<\/p>\n
      sleep -milliseconds 100<\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
    <\/pre>\n
<\/p>\n
    end<\/span> {<\/pre>\n
<\/p>\n
     Write-Host "ending Foo-C"<\/span> -ForegroundColor Cyan<\/pre>\n
<\/p>\n
    }<\/pre>\n
<\/p>\n
} #end C<\/span><\/pre>\n
<\/p>\n
 <\/pre>\n
<\/p>\n
 <\/pre>\n
<\/p>\n
Foo-A | Foo-B | Foo-C<\/pre>\n
<\/div>\n<\/div>\n
If you run:<\/p>\n
PS C:\\> Do-A | Do-B | Do-C<\/font><\/p>\n
You will see that the begin script blocks for B and C run first. End script blocks, by the way seem to run in order. You will see this behavior on PowerShell v1 and v2.<\/p>\n
If you run into any problems developing your own PowerShell solutions, please drop by the forums at ScriptingAnswers.com.<\/p>\n","protected":false},"excerpt":{"rendered":"
Last week I was helping someone out in the PowerShell forum at ScriptingAnswers.com. The specific problem is irrelevant;l however I  learned something in the process that will affect how I write my own PowerShell functions from now on. Not being a developer I never picked up on this subtle (at least to me) distinction. Here\u2019s…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[4,75,8],"tags":[32,98,534,82,540],"class_list":["post-544","post","type-post","status-publish","format-standard","hentry","category-powershell","category-powershell-v2-0","category-scripting","tag-functions","tag-pipeline","tag-powershell","tag-scriptblock","tag-scripting"],"yoast_head":"\nPotential Pipeline Pitfall • The Lonely Administrator<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/jdhitsolutions.com\/blog\/powershell\/544\/potential-pipeline-pitfall\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Potential Pipeline Pitfall • The Lonely Administrator\" \/>\n<meta property=\"og:description\" content=\"Last week I was helping someone out in the PowerShell forum at ScriptingAnswers.com. The specific problem is irrelevant;l however I  learned something in the process that will affect how I write my own PowerShell functions from now on. Not being a developer I never picked up on this subtle (at least to me) distinction. Here\u2019s...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/jdhitsolutions.com\/blog\/powershell\/544\/potential-pipeline-pitfall\/\" \/>\n<meta property=\"og:site_name\" content=\"The Lonely Administrator\" \/>\n<meta property=\"article:published_time\" content=\"2010-01-11T19:33:52+00:00\" \/>\n<meta name=\"author\" content=\"Jeffery Hicks\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@JeffHicks\" \/>\n<meta name=\"twitter:site\" content=\"@JeffHicks\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Jeffery Hicks\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/544\\\/potential-pipeline-pitfall\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/544\\\/potential-pipeline-pitfall\\\/\"},\"author\":{\"name\":\"Jeffery Hicks\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"headline\":\"Potential Pipeline Pitfall\",\"datePublished\":\"2010-01-11T19:33:52+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/544\\\/potential-pipeline-pitfall\\\/\"},\"wordCount\":529,\"commentCount\":4,\"publisher\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"keywords\":[\"functions\",\"Pipeline\",\"PowerShell\",\"ScriptBlock\",\"Scripting\"],\"articleSection\":[\"PowerShell\",\"PowerShell v2.0\",\"Scripting\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/544\\\/potential-pipeline-pitfall\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/544\\\/potential-pipeline-pitfall\\\/\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/544\\\/potential-pipeline-pitfall\\\/\",\"name\":\"Potential Pipeline Pitfall • The Lonely Administrator\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#website\"},\"datePublished\":\"2010-01-11T19:33:52+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/544\\\/potential-pipeline-pitfall\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/544\\\/potential-pipeline-pitfall\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/powershell\\\/544\\\/potential-pipeline-pitfall\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"PowerShell\",\"item\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/category\\\/powershell\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Potential Pipeline Pitfall\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/\",\"name\":\"The Lonely Administrator\",\"description\":\"Practical Advice for the Automating IT Pro\",\"publisher\":{\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/jdhitsolutions.com\\\/blog\\\/#\\\/schema\\\/person\\\/d0258030b41f07fd745f4078bdf5b6c9\",\"name\":\"Jeffery Hicks\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\",\"caption\":\"Jeffery Hicks\"},\"logo\":{\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Potential Pipeline Pitfall • The Lonely Administrator","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/jdhitsolutions.com\/blog\/powershell\/544\/potential-pipeline-pitfall\/","og_locale":"en_US","og_type":"article","og_title":"Potential Pipeline Pitfall • The Lonely Administrator","og_description":"Last week I was helping someone out in the PowerShell forum at ScriptingAnswers.com. The specific problem is irrelevant;l however I  learned something in the process that will affect how I write my own PowerShell functions from now on. Not being a developer I never picked up on this subtle (at least to me) distinction. Here\u2019s...","og_url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/544\/potential-pipeline-pitfall\/","og_site_name":"The Lonely Administrator","article_published_time":"2010-01-11T19:33:52+00:00","author":"Jeffery Hicks","twitter_card":"summary_large_image","twitter_creator":"@JeffHicks","twitter_site":"@JeffHicks","twitter_misc":{"Written by":"Jeffery Hicks","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/544\/potential-pipeline-pitfall\/#article","isPartOf":{"@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/544\/potential-pipeline-pitfall\/"},"author":{"name":"Jeffery Hicks","@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"headline":"Potential Pipeline Pitfall","datePublished":"2010-01-11T19:33:52+00:00","mainEntityOfPage":{"@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/544\/potential-pipeline-pitfall\/"},"wordCount":529,"commentCount":4,"publisher":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"keywords":["functions","Pipeline","PowerShell","ScriptBlock","Scripting"],"articleSection":["PowerShell","PowerShell v2.0","Scripting"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/jdhitsolutions.com\/blog\/powershell\/544\/potential-pipeline-pitfall\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/544\/potential-pipeline-pitfall\/","url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/544\/potential-pipeline-pitfall\/","name":"Potential Pipeline Pitfall • The Lonely Administrator","isPartOf":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#website"},"datePublished":"2010-01-11T19:33:52+00:00","breadcrumb":{"@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/544\/potential-pipeline-pitfall\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/jdhitsolutions.com\/blog\/powershell\/544\/potential-pipeline-pitfall\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/jdhitsolutions.com\/blog\/powershell\/544\/potential-pipeline-pitfall\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"PowerShell","item":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},{"@type":"ListItem","position":2,"name":"Potential Pipeline Pitfall"}]},{"@type":"WebSite","@id":"https:\/\/jdhitsolutions.com\/blog\/#website","url":"https:\/\/jdhitsolutions.com\/blog\/","name":"The Lonely Administrator","description":"Practical Advice for the Automating IT Pro","publisher":{"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/jdhitsolutions.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":["Person","Organization"],"@id":"https:\/\/jdhitsolutions.com\/blog\/#\/schema\/person\/d0258030b41f07fd745f4078bdf5b6c9","name":"Jeffery Hicks","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","url":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg","caption":"Jeffery Hicks"},"logo":{"@id":"https:\/\/secure.gravatar.com\/avatar\/832ae5d438fdcfc1420d720cd1991307927de8a0b12f2342e81c30f773e21098?s=96&d=wavatar&r=pg"}}]}},"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"jetpack-related-posts":[{"id":6348,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/6348\/building-more-powershell-functions\/","url_meta":{"origin":544,"position":0},"title":"Building More PowerShell Functions","author":"Jeffery Hicks","date":"January 3, 2019","format":false,"excerpt":"In a recent post I discussed the the process you might go through in developing a PowerShell function. By the end, I not only had a new tool for my PowerShell toolbox, but I had a function outline that I could re-use. If you read the previous article then you\u2026","rel":"","context":"In "PowerShell"","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/01\/image_thumb-3.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/01\/image_thumb-3.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/01\/image_thumb-3.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2019\/01\/image_thumb-3.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":840,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/840\/pipelines-consoles-and-hosts\/","url_meta":{"origin":544,"position":1},"title":"Pipelines, Consoles and Hosts","author":"Jeffery Hicks","date":"August 19, 2010","format":false,"excerpt":"I continue to come across a particular topic in discussion forums that causes many PowerShell beginners a lot of headaches and more than a little frustration. I know I've written about this before and I'm sure I'll cover it again, but when writing anything in PowerShell that you see in\u2026","rel":"","context":"In "PowerShell"","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2010\/08\/write-demo.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":5789,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/5789\/who_is_running\/","url_meta":{"origin":544,"position":2},"title":"Who is Running Your PowerShell Script?","author":"Jeffery Hicks","date":"November 21, 2017","format":false,"excerpt":"I've often talked about the benefit of including Verbose output in your PowerShell scripts and functions from the very beginning. This is especially helpful when someone else is running your command but encounters a problem. You can have them start a transcript, run your command with \u2013Verbose, close the transcript\u2026","rel":"","context":"In "PowerShell"","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"image","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2017\/11\/image_thumb-17.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2017\/11\/image_thumb-17.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2017\/11\/image_thumb-17.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2017\/11\/image_thumb-17.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":3722,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/3722\/reflections-on-the-powershell-scripting-games\/","url_meta":{"origin":544,"position":3},"title":"Reflections on the PowerShell Scripting Games","author":"Jeffery Hicks","date":"February 26, 2014","format":false,"excerpt":"During the most recent PowerShell Scripting Games, I was fortunate enough to be one of the judges. Now that the games have concluded I thought I'd share my reflections on the entries. Naturally these are merely my opinions but they are drawn from years of experience with PowerShell and almost\u2026","rel":"","context":"In "Best Practices"","block_context":{"text":"Best Practices","link":"https:\/\/jdhitsolutions.com\/blog\/category\/best-practices\/"},"img":{"alt_text":"talkbubble","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2011\/10\/talkbubble.png?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":7700,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7700\/active-directory-objects-and-the-powershell-pipeline\/","url_meta":{"origin":544,"position":4},"title":"Active Directory Objects and the PowerShell Pipeline","author":"Jeffery Hicks","date":"September 28, 2020","format":false,"excerpt":"This article is something I've been meaning to write for sometime. As often as I tell people PowerShell is easy to use once you understand its core concepts, that isn't always the case.\u00a0 This is a problem my friend Gladys Kravitz brought to my attention some time ago. Like her,\u2026","rel":"","context":"In "Active Directory"","block_context":{"text":"Active Directory","link":"https:\/\/jdhitsolutions.com\/blog\/category\/active-directory\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/09\/Get-bits-revised-ad.jpg?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/09\/Get-bits-revised-ad.jpg?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/09\/Get-bits-revised-ad.jpg?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/09\/Get-bits-revised-ad.jpg?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2020\/09\/Get-bits-revised-ad.jpg?resize=1050%2C600&ssl=1 3x"},"classes":[]},{"id":8693,"url":"https:\/\/jdhitsolutions.com\/blog\/powershell\/8693\/exporting-powershell-functions-to-files\/","url_meta":{"origin":544,"position":5},"title":"Exporting PowerShell Functions to Files","author":"Jeffery Hicks","date":"December 3, 2021","format":false,"excerpt":"When I write a PowerShell module, it typically includes more than one export function. Where you store your module functions is a great discussion topic and I don't think there is necessarily one best practice for everyone. I think it might depend on the number and complexity of the functions.\u2026","rel":"","context":"In "PowerShell"","block_context":{"text":"PowerShell","link":"https:\/\/jdhitsolutions.com\/blog\/category\/powershell\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2021\/12\/export-function3.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2021\/12\/export-function3.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2021\/12\/export-function3.png?resize=525%2C300&ssl=1 1.5x, https:\/\/i0.wp.com\/jdhitsolutions.com\/blog\/wp-content\/uploads\/2021\/12\/export-function3.png?resize=700%2C400&ssl=1 2x"},"classes":[]}],"_links":{"self":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/544","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/comments?post=544"}],"version-history":[{"count":0,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/544\/revisions"}],"wp:attachment":[{"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/media?parent=544"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/categories?post=544"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jdhitsolutions.com\/blog\/wp-json\/wp\/v2\/tags?post=544"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}