Geek Answers Handbook

The problem of integrating MSBuild and PSExec, the lack of quick output

We faced the problem of integrating MSBuild with PsExec . In our scenario, we run PsExec in the msbuild build file. The PsExec command runs another MSBuild file on the remote server to complete the task that we would like to see in the output.

<?xml version="1.0" encoding="utf-8"?> <Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> .... <Exec Command="$(PsExecPath) \\$(RemoteIP) -u $(Username) -p $(Password) -w $(RemoteWorkingDir) msbuild.exe fullbuild.xml /t:Release" > </Exec>

It works fine and it does not freeze, but the output of the remote msbuild command does not appear on the console. When I start psexec directly from the command line, it works fine and the output of the remote assembly appears on the screen.

We use PsExec 2.11 and MSBuild 4.0. What am I missing here?

+7
msbuild msbuild-task psexec
source share

No one has answered this question yet.

See related questions:

71
TeamCity says that instead of "/ property:" at the MSBuild step, "Build Parameters" should be used. What does it mean?
33
Can I deploy MSBuild using integrated authentication or just basic?
4
psexec inside visual studio
4
All Visual Studio 2013 builds now fail
4
PsExec from ant does not end
2
PsExec hangs without output if -d or -i is not used
2
msbuild builderror for standard library.net
one
PsExec does not detect that my C # console application has completed
one
Team City Version 9.0 freezes when PSEXEC command is executed
one
Call remote MSBuild script inside MSBuild script with cygwin sshd

More articles:


All Articles