I have a PowerShell script for building my project files, and I'd like to have capability to run it from my file manager's command line (and, possibly, make a shortcut to this script so I can start build from my desktop)
Any way to do this?
Windows – How to launch PowerShell script from the OS command line
command-line-interfacepowershellwindows
Related Solutions
You could run it silently using a Windows Script file instead. The Run Method allows you running a script in invisible mode. Create a .vbs file like this one
Dim WinScriptHost
Set WinScriptHost = CreateObject("WScript.Shell")
WinScriptHost.Run Chr(34) & "C:\Scheduled Jobs\mybat.bat" & Chr(34), 0
Set WinScriptHost = Nothing
and schedule it. The second argument in this example sets the window style. 0 means "hide the window."
Complete syntax of the Run method:
object.Run(strCommand, [intWindowStyle], [bWaitOnReturn])
Arguments:
- object: WshShell object.
- strCommand: String value indicating the command line you want to run. You must include any parameters you want to pass to the executable file.
- intWindowStyle: Optional. Integer value indicating the appearance of the program's window. Note that not all programs make use of this information.
- bWaitOnReturn: Optional. Boolean value indicating whether the script should wait for the program to finish executing before continuing to the next statement in your script. If set to true, script execution halts until the program finishes, and Run returns any error code returned by the program. If set to false (the default), the Run method returns immediately after starting the program, automatically returning 0 (not to be interpreted as an error code).
Related Topic
- PowerShell script, showing commands run
- Windows – How to run a PowerShell script from Cygwin SSH session
- PowerShell script works from command line, not from Task Scheduler. Why
- Windows – How to create a scheduled task from the command line that only runs on demand
- PowerShell Command ‘write-zip’ doesn’t work
Best Answer
If you want to make powershell scripts behave a little more like typical cmd\bat scripts where you can just type the name and have them execute you can set up the association and file type to tell the shell to pass the correct parameters to Powershell and set the patheext variable so you just have to type the name of the script rather than the full name.ext.
First check that the .ps1 extension is associated with Powershell - it should be but it's worth making sure:
This should give you something like the following:
Now override the default open behaviour (open with notepad) for this file type with the Powershell commandline syntax for calling a script. We need to add additional quotes around the parameter &1 to handle paths with spaces.
If you really want Powershell scripts to act like other script files then modify the pathext environment variable. Ideally set this in via My Computer->Properties->Advanced System Settings->Advanced tab->Environment Variables but you can temporarily set this in a cmd shell via: