title: How to force Asp.net development server to run as a 32-bit process?
body: <p>I am having problem getting the MS Visual Studio Remote Debugger to connect to my local IE instance as it is running as a 64-bit rather than a 32-bit process.</p>
  
  <p>Every time I try to run it currently in Visual Studio I get the 
  <code>The 32-bit version of the Visual Studio Remote Debugging Monitor (MSVSMON.EXE) cannot be used to debug 64-bit processes or 64-bit dumps".
  </code>
  error.</p>
  
  <p>Investigating a bit, I think I have narrowed it down to the web asp service being run as a x64 process rather than a x86 (which both Visual Studio, and the silver light application are running as). I confirmed it as running as a 64-bit process by trying to "attach" visual studio to the process when the application was running in the ASP.Net Development Server.</p>
  
  <p>In short: Is there a setting I am missing somewhere to force Visual Studio to run the ASP.Net service as a 32-bit process? I have read about using a variable in the web.config application pool to use 32-bit (via the enable32BitAppOnWin64 config option), but it seems to only work in IIS, not ASP.net Dev server.</p>
  
  <p>Any thoughts?</p>
  
  <p>Edit For Clarity:
  I am running Windows 7 64-bit, Visual Studio 2010 (which is running as a 32-bit process). Currently it is launching ASP.NET Development Server (not IIS) to host the back end web service. I am hoping I can simply "fix" this via a setting, but if not my backup would be to run IIS Express.</p>