title: Server Error in '/' Application after updating a dll in a C# .NET website project
body: <p>We have a C# .NET website which was developed and maintained by a third party. I'm due to take over the general upkeep soon, so am trying to get a system going where I can maintain a local copy and deploy updates to the website. We need to make it work for two of us to work on for at least another month, after that I'm on my own.</p>
  
  <p>We have an SVN of source, and an SVN of production published code. I can pull the solution and after some faffing I can make it build and run without problems locally. I'm using Visual Studio 2015, the target framework is 4.0.</p>
  
  <p>I can update cshtml files, build, publish locally, and then copy these files over the website published version and it runs fine. </p>
  
  <p>However, the bin/dlls that are produced, if copied into the website version, produces this fabulous error:</p>
  
  <pre><code>http://website.com/Error/InternalServerError?aspxerrorpath=/
  Server Error in '/' Application. Runtime Error. 
  Description: An exception occurred while processing your request. 
  Additionally, another exception occurred while executing the custom error page for the first exception. 
  The request has been terminated.
  </code></pre>
  
  <p>If I copy back the dlls from the original, it works fine. </p>
  
  <p>If I don't modify the code, but just build and publish the project, my dlls are still different sizes from the website versions. </p>
  
  <p>The developers are using Visual Studio 2012, is this a factor? Why are the dlls for my local version (that runs fine) different, if I download the source and build/publish it with no changes? </p>
  
  <p>The dlls in question by the way are a single one for the website itself, website.dll say, and one for 'objects' that they've dumped a load of functions into for doing various things, objects.dll, these are the only two I'm trying to copy over - all the other dlls match in size between my and the website versions.</p>
  
  <p>I'm pretty new to this so may be making some fundamental mistakes here, but if I am, then our developer isn't picking up on them. I mean, I'm kind of not surprised that they're different, surely you need to deploy the whole project, and not just drop some dlls into an existing published folder? My developer is saying that's the only way we can do it...</p>
  
  <p>Any tips of things I can try?</p>
  
  <p>Thanks in advance.</p>