CODEWITHSUNDEEP
c#visual-studiovisual-studio-2010msbuild
Tom
Tom

Reputation: 213

MSBuild behaves different on several machines

So I have a solution with 6 projects and one Webproject in it. Some referenced dll's in the webproject (ie Aspose.dll and Microsoft.Practices.ObjectBuilder2.dll) do not have copy local set to true in the project file, but when I open the solution on my local machine and look at the properties of the reference have set copy local to true.

We have several build machines, on some MSBuild consumes the dll and outputs it into the bin directory and on another is treats it as copy local = false.

When I open the solution on the build machine that is failing, the copy local to true setting is now removed and set to false, causing the build to fail. On all other machines it shows up as true.

Any suggestions on what might be causing this?

Upvotes: 1

Views: 263

Answers (1)

Squirrel
Squirrel

Reputation: 1296

One other tip is to make sure you don't reference things from the current directory in msbuild files - i.e. don't do "../../Xyz" but instead ground them against a 'known' directory like "$(MSBuildProjectDirectory)/../../Xyz" - that way when they're running in a variety of contexts (build agents) they should still do the right thing.

(Other well known properties: http://msdn.microsoft.com/en-us/library/ms164309.aspx )

Upvotes: 1

Related Questions