1. Powershell.exe Command Arguments
2. Call Powershell Script From Command Line

The is an escape character that is required due to PowerShell's use of CommandLineToArgvW to parse input arguments. Powershell.exe -Command Start-Process PowerShell -ArgumentList '-NoProfile -File 'C:long nametest one.ps1' -Verb RunAs Extending the above to pass quoted arguments to the script. You can use PowerShell.exe to start a Windows PowerShell session from the command line of another tool, such as Cmd.exe, or use it at the Windows PowerShell command line to start a new session. Use the parameters to customize the session. In PowerShell V2.0, if you are running 7z.exe (7-Zip.exe) or another command that starts with a number, you have to use the command invocation operator &. Things can get tricky when an external command has a lot of parameters or there are spaces in the arguments or paths! For years, I have used the cmd/DOS/Windows shell and passed command-line arguments to batch files. For example, I have a file, zuzu.bat and in it, I access%1,%2, etc.Now, I want to do the same when I call a PowerShell script when I am in a Cmd.exe shell.I have a script, xuxu.ps1 (and I've added PS1 to my PATHEXT variable and associated PS1 files with PowerShell).

For years, I have used the cmd/DOS/Windows shell and passed command-line arguments to batch files. For example, I have a file, zuzu.bat and in it, I access %1, %2, etc. Now, I want to do the same when I call a PowerShell script when I am in a Cmd.exe shell. I have a script, xuxu.ps1 (and I've added PS1 to my PATHEXT variable and associated PS1 files with PowerShell). But no matter what I do, I seem unable to get anything from the $args variable. It always has length 0.

If I am in a PowerShell shell, instead of cmd.exe, it works (of course). But I'm not yet comfortable enough to live in the PowerShell environment full time. I don't want to type powershell.exe -command xuxu.ps1 p1 p2 p3 p4. I want to type xuxu p1 p2 p3 p4.

Is this possible, and if so, how?

The sample I cannot get to work is trivial, foo.ps1:

The results are always like this:

YoungHobbitDaniel 'Dang' GriffithDaniel 'Dang' Griffith

7 Answers

Powershell.exe Command Arguments

This article helps. In particular, this section:

-File

Runs the specified script in the local scope ('dot-sourced'), so that the functions and variables that the script creates are available in the current session. Enter the script file path and any parameters. File must be the last parameter in the command, because all characters typed after the File parameter name are interpreted as the script file path followed by the script parameters.

i.e.

means run the file myfile.ps1 and arg1 arg2 & arg3 are the parameters for the PowerShell script.

ArjArj

OK, so first this is breaking a basic security feature in PowerShell. With that understanding, here is how you can do it:

1. Open an Windows Explorer window
2. Menu Tools ->Folder Options -> tab File Types
3. Find the PS1 file type and click the advanced button
4. Click the New button
5. For Action put: Open
6. For the Application put: 'C:WINNTsystem32WindowsPowerShellv1.0powershell.exe' '-file' '%1' %*

You may want to put a -NoProfile argument in there too depending on what your profile does.

Peter MortensenEBGreenEBGreen

After digging through the PowerShell documentation, I discovered some useful information about this issue. You can't use the $args if you used the param(..) at the beginning of your file; instead you will need to use $PSBoundParameters. I copy/pasted your code into a PowerShell script, and it worked as you'd expect in PowerShell version 2 (I am not sure what version you were on when you ran into this issue).

If you are using $PSBoundParameters (and this ONLY works if you are using param(..) at the beginning of your script), then it is not an array, it is a hash table, so you will need to reference it using the key / value pair.

And when called with..

Wipeout frames autocad. The result is..

Peter Mortensen

You could declare your parameters in the file, like param:

And then call the PowerShell file like so .temp.ps1 para1 para2..para10, etc.

V.BV.B

Maybe you can wrap the PowerShell invocation in a .bat file like so:

If you then placed this file under a folder in your PATH, you could call PowerShell scripts like this:

Quoting can get a little messy, though:

Peter Mortensenguillermoooguillermooo

You may not get 'xuxu p1 p2 p3 p4' as it seems. But when you are in PowerShell and you set

You can run those scripts like this:

or

Call Powershell Script From Command Line

or

I hope that makes you a bit more comfortable with PowerShell.

Austin T French

if you want to invoke ps1 scripts from cmd and pass arguments without invoking the script like

you can do the following

This is assuming powershell.exe is in your path

Not the answer you're looking for? Browse other questions tagged command-linepowershellarguments or ask your own question.