Well, from the doc: --- Does the exec task pass the integration properties via the command line?
No. The integration properties are only available as environment variables. As there is no way of knowing the way in which the external program expects these properties to be formatted as command line arguments, environment variables are a simple, common medium for making these values accessible. To pass these environment variables into an external program, have the exec task call a batch file instead that will pick up the environment variables, format them and pass them as command line arguments to the external program. --- Can you have your build script read the environment variables? Also, you may want to try the nant or msbuid task. The command line of tfsbuild seems similar to those and all those variables are passed on the command line. BOb On Dec 23, 10:21 am, Borodkin <[email protected]> wrote: > I used project configuration like this to pass CCNetLabel to > TFSBuild.exe, but it does not work: > <executable>C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE > \TFSBuild.exe</executable> > <buildArgs>start "http://TFSSERVER:8080"; ROOT > "ROOT_NightlyBuilds" /msbuildarguments:"/p:CCNetLabel=%CCNetLabel%</ > buildArgs> > > I've solved this problem using bach file, but I hope to find better > solution, without additional files. > > BATCH: > "C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE > \TFSBuild.exe" start "http://TFSSERVER:8080"; %TEAMPROJECT% > %DEFINITIONNAME% /msbuildarguments:"/p:CCNetLabel=%CCNetLabel%"
