Deadly-Bagel almost had it I think. Don't use double quotes in $outputpath to keep Get-Content happy, but add them in your argument list string.

Be sure to escape with backtick `. In fact you might just want to do that with all the paths:

$outputpath = 'C:\Users\bob\Desktop\output new.xml'
Start -FilePath $sqlpackage -ArgumentList "/action:DeployReport /SourceFile:`"$dacpacpath`" /Profile:`"$profilepath`" /OutputPath:`"$outputpath`"" -NoNewWindow -Wait

[xml]$xmldocument = Get-Content -Path $outputpath

Hi @AATester

Thanks for writing and I'm happy to help you today regarding running your power shell script.

In case you want to run powershell.exe -File from the command line, you always have to set paths with spaces in double quotes ("").

Also try using the Grave Accent Character () PowerShell uses the grave accent () character as its escape character. Just add it before each space in the file name. (You’ll find this character above the Tab key and below the Esc key on your keyboard.)

WshShell.Run("powershell -file \"" + pathvar + "\*My `  Tests*\\PickupTest.ps1")  

Here is a helpful page with information about Windows PowerShell

https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/powershell

------------

--If the reply is helpful, please Upvote and Accept as answer.--

$msbuild = "${env:ProgramFiles(x86)}" + '\MSBuild\14.0\Bin\MSBuild.exe'

Try this way. No spaces, so path should be fine.

The easiest solution is to use single-quoting ('...') for the embedded strings:

powershell -ExecutionPolicy Unrestricted "Start-Process -Path program.exe -ArgumentList 'C:\Program Files\somefile.txt', 'Run'"

Since it is PowerShell that will be interpreting the command string, it recognizes the embedded '...' strings as string literals.

If you try to embed double-quoted strings ("..."), you face two hurdles:

• First, PowerShell's CLI requires \ as the escape character for " (whereas internally it is `), so you need to escape the " inside the overall "..." command string as \".

• Additionally, due to a known problem with Start-Process, you need an extra round of escaping, which makes the solution quite obscure and unwieldy, because you must escape each embedded " as \"`\" (!).

powershell -ExecutionPolicy Unrestricted "Start-Process -Path program.exe -ArgumentList \"`\"C:\Program Files\somefile.txt\"`\", \"`\"Run\"`\" "

Would this do what you want?:

& "C:\Windows Services\MyService.exe"

Use &, the call operator, to invoke commands whose names or paths are stored in quoted strings and/or are referenced via variables, as in the accepted answer. Invoke-Expression is not only the wrong tool to use in this particular case, it should generally be avoided.