Im using an msbuild script to do my build and because it includes an msi installer im using the devenv.exe method to compile the solution. I have had this previously working but since then ive moved the checkout folder of teamcity and updated the paths in the msbuild script to reflect that change and now my build fails with:

Now i dont underwstand why its even looking in a \Debug\ folder at all as ive specifically told it to run the Release configuration! but more to the point why is it copying the MBBuild script after the build???[12:03:45]: [Exec] "C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe" "C:\vjtech\dev\Clisp2010Change\Clisp\Clisp.Studio\Clisp.Studio.sln" /Build Release /out "C:\vjtech\dev\Clisp2010Change\Clisp\Clisp.Studio\Clisp.Studio.txt"

Votes

Share

It seems that you are passing in Release as a configuration for the build but then trying to get the compilation from Debug. If the Release configuration means building the project in release format then it may not be in the debug folder. If this is the case then I think you need to make your build script a little less specific and use something like bin\{configuration}

this is just my point, im not asking it to come from anywhere TC is doing that!

in msbuild i tell it to do a release config build (which it succesfully does),but the MSBuild Exec task im using is failing becuase after building TC is trying to copy the build script (having added an extension of .exe) to another folder? i never anywhere in my msbuild script to do that.

not knowing what caused this to stop working and thinking it might have been a recent upgrade to TC from 5.2 to 6.0.3 i reverted all build script changes and the old one is now working again....?? i will diff the files and see what the changes are (though i already know it was only an source code path) and the matching change in TC. but ill report back as i this is almost impossible to debug

$(MSBuildProjectFile) or similar wellknown parameters are affected by msbuild runner under TeamCity. TeamCity MSBuild runner generates wrapping MSBuild script for your own script. This lead to changes in wellknown properties values in the build.

In TeamCity 6.5 you may disable wrapper generation by setting teamcity.msbuild.generateWrappingScript configuration parameter to false. Please note, this wrapping script was generated since early time as that was not changed between 5.0 and 6.0.