I was able to make it work putting in custom command this line:
powershell -command Invoke-Expression \"& 'c:\Program Files (x86)\Microsoft
Visual Studio\2019\Professional\MSBuild\Current\Bin\amd64\msbuild.exe'\"
Please note escape "\" on double quotes.
This is my workaround.
I still do not
Il giorno giovedì 24 febbraio 2022 alle 11:38:05 UTC+1 ashwant...@gmail.com
ha scritto:
> There is a comment with a possible workaround on the linked issue -
> https://github.com/gocd/gocd/issues/4173#issuecomment-596109199. Have you
> tried that?
>
Yes infact I replied there that the
There is a comment with a possible workaround on the linked issue -
https://github.com/gocd/gocd/issues/4173#issuecomment-596109199. Have you
tried that?
We've a similar problem with linux based systems as well. As a general rule
I always wrap all my commands inside a shell script (or in your
Hello,
I have a windows task with this custom command:
C:\'Program Files (x86)'\'Microsoft Visual
Studio'\2019\Community\MSBuild\Current\Bin\msbuild.exe
The command has spaces in path. When I launch it in some windows 10 pcs it
works correctly in others it says that x86 is wrong argument. It