Question:
Is there a way to suppress the enclosing quotation marks around each command-line argument that PowerShell likes to generate and then pass to external executables for command-line arguments that have spaces in them?
Here’s the situation:
One way to unpack many installers is a command of the form:
|
1 2 |
msiexec /a |
Trying to execute this from PowerShell has proven quite difficult. PowerShell likes to enclose parameters with spaces in double-quotes. The following lines:
|
1 2 3 4 5 6 7 8 |
msiexec /a somepackage.msi /qn 'TARGETDIR="c:\some path"' msiexec /a somepackage.msi /qn $('TARGETDIR="c:\some path"') $td = '"c:\some path"' msiexec /a somepackage.msi /qn TARGETDIR=$td |
All result in the following command line (as reported by the Win32 GetCommandLine() API):
|
1 2 |
"msiexec" /a somepackage.msi /qn "TARGETDIR="c:\some path"" |
This command line:
|
1 2 |
msiexec /a somepackage.msi TARGETDIR="c:\some path" /qn |
results in
|
1 2 |
"msiexec" /a fooinstaller.msi "TARGETDIR=c:\some path" /qn |
It seems that PowerShell likes to enclose the results of expressions meant to represent one argument in quotation marks when passing them to external executables. This works fine for most executables. However, MsiExec is very specific about the quoting rules it wants and won’t accept any of the command lines PowerShell generates for paths have have spaces in them.
Is there a way to suppress this behavior?
Answer:
Escape the inner quotes like this:
|
1 2 |
msiexec /a somepackage.msi TARGETDIR=`"c:\some path`" /qn |