title: VS2010 compiles solution without errors, msbuild fails: "fatal error CS0002: Unable to load message string from resources"
body: <p>I'm having a lot of trouble trying to track down the cause of this error message. I have a large Visual Studio 2010 solution which compiles without error on my local machine but on the build server, msbuild fails on one of the projects with the error:</p>
  
  <p><strong>fatal error CS0002: Unable to load message string from resources</strong></p>
  
  <p>Here's the red error section at the end:</p>
  
  <pre><code>Build FAILED.
  
  "C:\TeamCity\buildAgent\work\85eff164854b9e67\Libraries\Domainface.Proxy.Common\Domainface.Proxy.Common.csproj" (default target) (9) -&gt;
  (CoreCompile target) -&gt; 
    CSC : fatal error CS0002: Unable to load message string from resources. [C:\TeamCity\buildAgent\work\85eff164854b9e67\Libraries\Domainface.Proxy.Common\Domainface.Proxy.Common.csproj]
  
      0 Warning(s)
      1 Error(s)
  </code></pre>
  
  <p>The entire msbuild output from the build server is here: <a href="http://pastie.org/3660842" rel="nofollow">http://pastie.org/3660842</a></p>
  
  <p>What does the error generally refer to, that would cause it to build locally but not on the build server?</p>
  
  <p><strong>UPDATE</strong></p>
  
  <p>I have just run <code>msbuild /version</code> on both machines and it turns out the .net framework versions are very slightly different. Local machine is <code>4.0.30319.488</code> and build server is <code>4.0.30319.1</code>. I'm about to run windows update on the server to allow it to install some updates, as several seem to be .net framework-related, so I'll see if that makes a difference.</p>
  
  <p><strong>UPDATE</strong></p>
  
  <p>Installing the updates didn't help. Just remembered I copied up csc.exe from the async preview a little while ago in order to facilitate async compilation (the actual async preview had failed to install on the server due to visual studio not being there, but installing visual studio team viewer seems to have fixed that, so i've just run the proper async ctp3 installer to see if that makes a difference.</p>