Set up PowerShell Script for Automatic Execution

I have a few lines of PowerShell code that I would like to use as an automated script. The way I would like it to be able to work is to be able to call it using one of the following options:

1. One command line that opens PowerShell, executes script and closes PowerShell (this would be used for a global build-routine)
2. A file that I can double-click to run the above (I would use this method when manually testing components of my build process)

I have been going through PowerShell documentation online, and although I can find lots of scripts, I have been unable to find instructions on how to do what I need. Thanks for the help.

Save your script as a .ps1 file and launch it using powershell.exe, like this:

powershell.exe .\foo.ps1

Make sure you specify the full path to the script, and make sure you have set your execution policy level to at least "RemoteSigned" so that unsigned local scripts can be run.

[Source][1] for Matt's answer.

I can get it to run by double-clicking a file by creating a batch file with the following in it:

C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe LocationOfPS1File


[1]:

[To see links please register here]

From

[To see links please register here]

If you're willing to sully your beautiful PowerShell script with a little CMD, you can use a PowerShell-CMD polyglot trick. Save your PowerShell script as a .CMD file, and put this line at the top:

<pre>
@PowerShell -ExecutionPolicy Bypass -Command Invoke-Expression $('$args=@(^&{$args} %*);'+[String]::Join(';',(Get-Content '%~f0') -notmatch '^^@PowerShell.*EOF$')) & goto :EOF
</pre>

If you need to support quoted arguments, there's a longer version, which also allows comments. (note the unusual CMD commenting trick of double @).

<pre>
@@:: This prolog allows a PowerShell script to be embedded in a .CMD file.
@@:: Any non-PowerShell content must be preceeded by "@@"
@@setlocal
@@set POWERSHELL_BAT_ARGS=%*
@@if defined POWERSHELL_BAT_ARGS set POWERSHELL_BAT_ARGS=%POWERSHELL_BAT_ARGS:"=\"%
@@PowerShell -ExecutionPolicy Bypass -Command Invoke-Expression $('$args=@(^&{$args} %POWERSHELL_BAT_ARGS%);'+[String]::Join(';',$((Get-Content '%~f0') -notmatch '^^@@'))) & goto :EOF
</pre>

Run Script Automatically From Another Script (e.g. Batch File)
--
As Matt Hamilton suggested, simply create your PowerShell .ps1 script and call it using:

PowerShell C:\Path\To\YourPowerShellScript.ps1

or if your batch file's working directory is the same directory that the PowerShell script is in, you can use a relative path:

PowerShell .\YourPowerShellScript.ps1

And before this will work you will need to set the PC's Execution Policy, which I show how to do down below.

---

Run Script Manually Method 1
--

You can [see my blog post for more information][1], but essentially create your PowerShell .ps1 script file to do what you want, and then create a .cmd batch file in the same directory and use the following for the file's contents:

@ECHO OFF
SET ThisScriptsDirectory=%~dp0
SET PowerShellScriptPath=%ThisScriptsDirectory%MyPowerShellScript.ps1
PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& '%PowerShellScriptPath%'"

Replacing **MyPowerShellScript.ps1** on the 3rd line with the file name of your PowerShell script.

This will allow you to simply double click the batch file to run your PowerShell script, and will avoid you having to change your PowerShell Execution Policy.

My blog post also shows how to run the PowerShell script as an admin if that is something you need to do.

---

Run Script Manually Method 2
--
Alternatively, if you don't want to create a batch file for each of your PowerShell scripts, you can change the default PowerShell script behavior from Edit to Run, allowing you to double-click your .ps1 files to run them.

There is an additional registry setting that you will want to modify so that you can run scripts whose file path contains spaces. I show how to do both of these things [on this blog post][2].

With this method however, you will first need to set your execution policy to allow scripts to be ran. You only need to do this once per PC and it can be done by running this line in a PowerShell command prompt.

Start-Process PowerShell -ArgumentList 'Set-ExecutionPolicy RemoteSigned -Force' -Verb RunAs

**Set-ExecutionPolicy RemoteSigned -Force** is the command that actually changes the execution policy; this sets it to *RemoteSigned*, so you can change that to something else if you need. Also, this line will automatically run PowerShell as an admin for you, which is required in order to change the execution policy.

[1]:

[To see links please register here]

[2]:

[To see links please register here]

you can use this command :
powershell.exe -argument c:\scriptPath\Script.ps1