title: Visual Studio 2008 Performance Profiler Problems with ASP.NET
body: <p>I've been trying, and failing, to get VS.NET 2008 to profile an ASP.NET MVC application. When I try and start a profiling session I get a generic server 500 error from VS.NET:</p>
  
  <p>The web site could not be configured correctly; getting ASP.NET process information failed. Requesting '<a href="http://localhost:4750/foo/VSEnterpriseHelper.axd" rel="nofollow noreferrer">http://localhost:4750/foo/VSEnterpriseHelper.axd</a>' returned an error: The remote server returned an error: (500) Internal Server Error.</p>
  
  <p>I've tried several things, including:</p>
  
  <ul>
  <li>ensuring that web.config is writable</li>
  <li>ensuring that there aren't any permissions issues (everything is running as me, I'm an admin, and UAC is off)</li>
  <li>everything mentioned here:
  <a href="https://stackoverflow.com/questions/260432/500-error-running-visual-studio-asp-net-unit-test">500 Error Running Visual Studio ASP.NET Unit Test</a></li>
  </ul>
  
  <p>A brand new ASP.NET MVC app (i.e. File | New | Project ) will profile without problem, so I know my machine is capable of profiling such an app.</p>
  
  <p>So, my question here is what are the other common and uncommon things that can prevent VS.NET from starting a profiling session on an ASP.NET app?</p>