Visual Studio 2008 and its CopyLocal setting

posted by Dean on 31 Mar 2009.  Add a Comment

Tags: ,

Our build server wasn’t producing the same results as our local development machines. The same C# code yielded two different sets of code libraries. After much head-banging and hand-wringing, we finally traced the problem to an obscure error in the way Visual Studio 2008 handles .csproj files.

Basically, the Visual Studio IDE doesn’t handle the CopyLocal setting properly. This post from paraesthesia set us on the right track.

I have no idea what caused the problem. We had the same versions of the .NET Framework and Visual Studio 2008 installed on all our machines. The code was exactly the same. Apart from the build machine being Windows Server 2003 and out development machines being Windows XP, I can’t think of any other differences. But somehow the code libraries weren’t getting copied in the same way.

Just another adventure on our way toward the Beta release…

Related Posts

  1. Visual Studio 2008 and the CopyLocal setting
  2. 3 Useful Visual Studio Tricks for Spark Templates
  3. How to avoid Visual Studio Help
  4. Tools: Add In Express
  5. Looking for an IIS Alternative

Leave a Reply