Powershell Copy-Item Exit code 1









up vote
1
down vote

favorite
1












I have a script with several files I'd like to copy and I do it more or less like so.



Copy-Item xxx1 yyy1 -Force
Copy-Item xxx2 yyy2 -Force
Copy-Item xxx3 yyy3 -Force
Copy-Item xxx4 yyy4 -Force


and so on.



Now I'd like this script to exit with 1 if any of the files was not copied.



Thanks in advance










share|improve this question

























    up vote
    1
    down vote

    favorite
    1












    I have a script with several files I'd like to copy and I do it more or less like so.



    Copy-Item xxx1 yyy1 -Force
    Copy-Item xxx2 yyy2 -Force
    Copy-Item xxx3 yyy3 -Force
    Copy-Item xxx4 yyy4 -Force


    and so on.



    Now I'd like this script to exit with 1 if any of the files was not copied.



    Thanks in advance










    share|improve this question























      up vote
      1
      down vote

      favorite
      1









      up vote
      1
      down vote

      favorite
      1






      1





      I have a script with several files I'd like to copy and I do it more or less like so.



      Copy-Item xxx1 yyy1 -Force
      Copy-Item xxx2 yyy2 -Force
      Copy-Item xxx3 yyy3 -Force
      Copy-Item xxx4 yyy4 -Force


      and so on.



      Now I'd like this script to exit with 1 if any of the files was not copied.



      Thanks in advance










      share|improve this question













      I have a script with several files I'd like to copy and I do it more or less like so.



      Copy-Item xxx1 yyy1 -Force
      Copy-Item xxx2 yyy2 -Force
      Copy-Item xxx3 yyy3 -Force
      Copy-Item xxx4 yyy4 -Force


      and so on.



      Now I'd like this script to exit with 1 if any of the files was not copied.



      Thanks in advance







      powershell copy-item






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 11 at 12:36









      Icen

      15719




      15719






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote



          accepted










          What you're asking for is similar to the set -e option in bash, which causes a script to exit instantly in the event that a command signals failure (except in conditionals)[1].



          PowerShell has no such option[2], but you can emulate it:



          # Set up a trap (handler for when terminating errors occur).
          Trap
          # Print the error.
          # IMPORTANT: -ErrorAction Continue must be used, because Write-Error
          # itself would otherwise cause a terminating error too.
          Write-Error $_ -ErrorAction Continue
          exit 1


          # Make non-terminating errors terminating.
          $ErrorActionPreference = 'Stop'

          # Based on $ErrorActionPreference = 'Stop', any error reported by
          # Copy-Item will now cause a terminating error that triggers the Trap
          # handler.
          Copy-Item xxx1 yyy1 -Force
          Copy-Item xxx2 yyy2 -Force
          Copy-Item xxx3 yyy3 -Force
          Copy-Item xxx4 yyy4 -Force

          # Handle failure of an external program.
          foo.exe -bar
          if ($LASTEXITCODE -ne 0) Throw "foo failed." # Trigger the trap.

          # Signal success.
          exit 0


          Note:



          • PowerShell-internally, exit codes are not used in error handling; they typically only come into play when invoking external programs from PowerShell, or when PowerShell / a PowerShell script needs to signal success vs. failure for the outside world (when called from another shell, such as cmd on Windows, or bash on Unix-like platforms).


          • PowerShell's automatic $LASTEXITCODE variable reflects the exit code of the most recently executed external program / PowerShell script that called exit <n>.


          • Calls to external (console/terminal) programs that signal failure via a nonzero exit code do not trigger the trap block, hence the explicit throw statement in the snippet above.


          • Unless you set the exit code explicitly, it is the exit code of whatever external program happened to execute last that determines the script's overall exit code.


          [1] Note that this option has its critics, because the exact rules around when a failure is tolerated and when it causes a script to abort are hard to remember - see http://mywiki.wooledge.org/BashFAQ/105



          [2] Potentially adding support for it is being discussed in this GitHub issue.






          share|improve this answer


















          • 1




            My pleasure, @Icen; glad to hear it was helpful.
            – mklement0
            Nov 13 at 12:32










          Your Answer






          StackExchange.ifUsing("editor", function ()
          StackExchange.using("externalEditor", function ()
          StackExchange.using("snippets", function ()
          StackExchange.snippets.init();
          );
          );
          , "code-snippets");

          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "1"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53248823%2fpowershell-copy-item-exit-code-1%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          1
          down vote



          accepted










          What you're asking for is similar to the set -e option in bash, which causes a script to exit instantly in the event that a command signals failure (except in conditionals)[1].



          PowerShell has no such option[2], but you can emulate it:



          # Set up a trap (handler for when terminating errors occur).
          Trap
          # Print the error.
          # IMPORTANT: -ErrorAction Continue must be used, because Write-Error
          # itself would otherwise cause a terminating error too.
          Write-Error $_ -ErrorAction Continue
          exit 1


          # Make non-terminating errors terminating.
          $ErrorActionPreference = 'Stop'

          # Based on $ErrorActionPreference = 'Stop', any error reported by
          # Copy-Item will now cause a terminating error that triggers the Trap
          # handler.
          Copy-Item xxx1 yyy1 -Force
          Copy-Item xxx2 yyy2 -Force
          Copy-Item xxx3 yyy3 -Force
          Copy-Item xxx4 yyy4 -Force

          # Handle failure of an external program.
          foo.exe -bar
          if ($LASTEXITCODE -ne 0) Throw "foo failed." # Trigger the trap.

          # Signal success.
          exit 0


          Note:



          • PowerShell-internally, exit codes are not used in error handling; they typically only come into play when invoking external programs from PowerShell, or when PowerShell / a PowerShell script needs to signal success vs. failure for the outside world (when called from another shell, such as cmd on Windows, or bash on Unix-like platforms).


          • PowerShell's automatic $LASTEXITCODE variable reflects the exit code of the most recently executed external program / PowerShell script that called exit <n>.


          • Calls to external (console/terminal) programs that signal failure via a nonzero exit code do not trigger the trap block, hence the explicit throw statement in the snippet above.


          • Unless you set the exit code explicitly, it is the exit code of whatever external program happened to execute last that determines the script's overall exit code.


          [1] Note that this option has its critics, because the exact rules around when a failure is tolerated and when it causes a script to abort are hard to remember - see http://mywiki.wooledge.org/BashFAQ/105



          [2] Potentially adding support for it is being discussed in this GitHub issue.






          share|improve this answer


















          • 1




            My pleasure, @Icen; glad to hear it was helpful.
            – mklement0
            Nov 13 at 12:32














          up vote
          1
          down vote



          accepted










          What you're asking for is similar to the set -e option in bash, which causes a script to exit instantly in the event that a command signals failure (except in conditionals)[1].



          PowerShell has no such option[2], but you can emulate it:



          # Set up a trap (handler for when terminating errors occur).
          Trap
          # Print the error.
          # IMPORTANT: -ErrorAction Continue must be used, because Write-Error
          # itself would otherwise cause a terminating error too.
          Write-Error $_ -ErrorAction Continue
          exit 1


          # Make non-terminating errors terminating.
          $ErrorActionPreference = 'Stop'

          # Based on $ErrorActionPreference = 'Stop', any error reported by
          # Copy-Item will now cause a terminating error that triggers the Trap
          # handler.
          Copy-Item xxx1 yyy1 -Force
          Copy-Item xxx2 yyy2 -Force
          Copy-Item xxx3 yyy3 -Force
          Copy-Item xxx4 yyy4 -Force

          # Handle failure of an external program.
          foo.exe -bar
          if ($LASTEXITCODE -ne 0) Throw "foo failed." # Trigger the trap.

          # Signal success.
          exit 0


          Note:



          • PowerShell-internally, exit codes are not used in error handling; they typically only come into play when invoking external programs from PowerShell, or when PowerShell / a PowerShell script needs to signal success vs. failure for the outside world (when called from another shell, such as cmd on Windows, or bash on Unix-like platforms).


          • PowerShell's automatic $LASTEXITCODE variable reflects the exit code of the most recently executed external program / PowerShell script that called exit <n>.


          • Calls to external (console/terminal) programs that signal failure via a nonzero exit code do not trigger the trap block, hence the explicit throw statement in the snippet above.


          • Unless you set the exit code explicitly, it is the exit code of whatever external program happened to execute last that determines the script's overall exit code.


          [1] Note that this option has its critics, because the exact rules around when a failure is tolerated and when it causes a script to abort are hard to remember - see http://mywiki.wooledge.org/BashFAQ/105



          [2] Potentially adding support for it is being discussed in this GitHub issue.






          share|improve this answer


















          • 1




            My pleasure, @Icen; glad to hear it was helpful.
            – mklement0
            Nov 13 at 12:32












          up vote
          1
          down vote



          accepted







          up vote
          1
          down vote



          accepted






          What you're asking for is similar to the set -e option in bash, which causes a script to exit instantly in the event that a command signals failure (except in conditionals)[1].



          PowerShell has no such option[2], but you can emulate it:



          # Set up a trap (handler for when terminating errors occur).
          Trap
          # Print the error.
          # IMPORTANT: -ErrorAction Continue must be used, because Write-Error
          # itself would otherwise cause a terminating error too.
          Write-Error $_ -ErrorAction Continue
          exit 1


          # Make non-terminating errors terminating.
          $ErrorActionPreference = 'Stop'

          # Based on $ErrorActionPreference = 'Stop', any error reported by
          # Copy-Item will now cause a terminating error that triggers the Trap
          # handler.
          Copy-Item xxx1 yyy1 -Force
          Copy-Item xxx2 yyy2 -Force
          Copy-Item xxx3 yyy3 -Force
          Copy-Item xxx4 yyy4 -Force

          # Handle failure of an external program.
          foo.exe -bar
          if ($LASTEXITCODE -ne 0) Throw "foo failed." # Trigger the trap.

          # Signal success.
          exit 0


          Note:



          • PowerShell-internally, exit codes are not used in error handling; they typically only come into play when invoking external programs from PowerShell, or when PowerShell / a PowerShell script needs to signal success vs. failure for the outside world (when called from another shell, such as cmd on Windows, or bash on Unix-like platforms).


          • PowerShell's automatic $LASTEXITCODE variable reflects the exit code of the most recently executed external program / PowerShell script that called exit <n>.


          • Calls to external (console/terminal) programs that signal failure via a nonzero exit code do not trigger the trap block, hence the explicit throw statement in the snippet above.


          • Unless you set the exit code explicitly, it is the exit code of whatever external program happened to execute last that determines the script's overall exit code.


          [1] Note that this option has its critics, because the exact rules around when a failure is tolerated and when it causes a script to abort are hard to remember - see http://mywiki.wooledge.org/BashFAQ/105



          [2] Potentially adding support for it is being discussed in this GitHub issue.






          share|improve this answer














          What you're asking for is similar to the set -e option in bash, which causes a script to exit instantly in the event that a command signals failure (except in conditionals)[1].



          PowerShell has no such option[2], but you can emulate it:



          # Set up a trap (handler for when terminating errors occur).
          Trap
          # Print the error.
          # IMPORTANT: -ErrorAction Continue must be used, because Write-Error
          # itself would otherwise cause a terminating error too.
          Write-Error $_ -ErrorAction Continue
          exit 1


          # Make non-terminating errors terminating.
          $ErrorActionPreference = 'Stop'

          # Based on $ErrorActionPreference = 'Stop', any error reported by
          # Copy-Item will now cause a terminating error that triggers the Trap
          # handler.
          Copy-Item xxx1 yyy1 -Force
          Copy-Item xxx2 yyy2 -Force
          Copy-Item xxx3 yyy3 -Force
          Copy-Item xxx4 yyy4 -Force

          # Handle failure of an external program.
          foo.exe -bar
          if ($LASTEXITCODE -ne 0) Throw "foo failed." # Trigger the trap.

          # Signal success.
          exit 0


          Note:



          • PowerShell-internally, exit codes are not used in error handling; they typically only come into play when invoking external programs from PowerShell, or when PowerShell / a PowerShell script needs to signal success vs. failure for the outside world (when called from another shell, such as cmd on Windows, or bash on Unix-like platforms).


          • PowerShell's automatic $LASTEXITCODE variable reflects the exit code of the most recently executed external program / PowerShell script that called exit <n>.


          • Calls to external (console/terminal) programs that signal failure via a nonzero exit code do not trigger the trap block, hence the explicit throw statement in the snippet above.


          • Unless you set the exit code explicitly, it is the exit code of whatever external program happened to execute last that determines the script's overall exit code.


          [1] Note that this option has its critics, because the exact rules around when a failure is tolerated and when it causes a script to abort are hard to remember - see http://mywiki.wooledge.org/BashFAQ/105



          [2] Potentially adding support for it is being discussed in this GitHub issue.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 11 at 21:11

























          answered Nov 11 at 12:51









          mklement0

          123k20235265




          123k20235265







          • 1




            My pleasure, @Icen; glad to hear it was helpful.
            – mklement0
            Nov 13 at 12:32












          • 1




            My pleasure, @Icen; glad to hear it was helpful.
            – mklement0
            Nov 13 at 12:32







          1




          1




          My pleasure, @Icen; glad to hear it was helpful.
          – mklement0
          Nov 13 at 12:32




          My pleasure, @Icen; glad to hear it was helpful.
          – mklement0
          Nov 13 at 12:32

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53248823%2fpowershell-copy-item-exit-code-1%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          這個網誌中的熱門文章

          How to read a connectionString WITH PROVIDER in .NET Core?

          In R, how to develop a multiplot heatmap.2 figure showing key labels successfully

          Museum of Modern and Contemporary Art of Trento and Rovereto