title: COMPILATION debug=false is killing my ASP.NET site
body: <p>I have a large (to me) ASP.NET (4.5 Framework) application that was working fine when developed in and published from VS2012.</p>
  
  <p>I've since upgraded from VS2012 to VS2013 and I opened the solution without issue and it runs fine locally (on IIS Express).</p>
  
  <p>I don't know if this is a red-herring, but I used NuGet to update the AJAX Control Toolkit for the first time (and its dependencies) and it appears to have worked.</p>
  
  <p>When I publish (file system publish) the site to our web server (IIS 8 in Windows Server 2012) it loads fine UNTIL I change <code>&lt;compilation defaultLanguage="vb" debug="true" targetFramework="4.5"&gt;</code> to <code>debug="false"</code>.<br>
  When I do, the site runs like a pig, sometimes pages don't even load, and its IIS Worker Process spikes the CPU and holds, growing in % until it consumes essentially all the CPU.</p>
  
  <p>EDIT: this happens on the server and on my PC (IIS Express)</p>
  
  <p>This test site's AppPool is running with the identical settings as our live site's AppPool. Of note:</p>
  
  <ul>
  <li>Enable 32-bit applications: True</li>
  <li>.NET Framework Version: v4.0</li>
  <li>Managed Pipeline Mode: Integrated</li>
  </ul>
  
  <p>I expect you'll need more information, but I honestly don't know where to begin and I don't want to overwhelm with unnecessary detail.<br>
  Thank you in advance</p>
  
  <p>EDIT: I REALLY should have mentioned this:<br>
  the site is precompiled during publish in Release mode. I've never had to change to debug=false in my development environment prior to publish in the past.</p>
  
  <p>I get this for each of the Projects in my solution:
  <code>(0,0): warning : The following assembly has dependencies on a version of the .NET Framework that is higher than the target and might not load correctly during runtime causing a failure: [projectname], Version=1.0.0.0, Culture=neutral, PublicKeyToken=null. The dependencies are: Microsoft.VisualBasic, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a. You should either ensure that the dependent assembly is correct for the target framework, or ensure that the target framework you are addressing is that of the dependent assembly.</code></p>
  
  <p><strong>EDIT:</strong> it appears this solution I inherited is a web SITE not APP. I don't know if that comes into play.</p>