Migrating to PowerShell? Don't Scrap Your Existing Code Just Yet

Executive Summary:

Migrating to the Windows PowerShell command line interface (CLI) shell and scripting language can be a simple transition.

In Windows PowerShell, you can run your preexisting batch (.cmd and .bat) and script (.vbs and .js) files.

You can also incorporate these files’ output into the Windows PowerShell pipeline.

Alternatively, you can integrate batch commands and script statements directly into your PowerShell code.

You’ve read the articles. Tested the product. Created the scripts. And now you’re convinced. Windows PowerShell promises to be everything you’ve heard it would be. But you were also convinced when you plunged into VBScript—you were even convinced when you wrote all those batch files. So what do you do with your old script and batch files if you switch to PowerShell? You have two choices: Rewrite everything in the PowerShell scripting language, or leverage the power in PowerShell and go right on using that original code. . . .