Fresh Windows 7 x64 install, Visual Studio 2008 debugger won't attach/fails to hit breakpoint

Question

Hi all,

Was forced to move from 32-bit Vista to Windows 7 x64 over the weekend, and now when trying to debug a web app, the debugger won't launch if I use Debugger.Launch(), and breakpoints aren't hit when I manually attach to w3wp.exe. After the page in question loads, w3wp.exe no longer appears in the processes window even though the page will continue to load (not cached). Yes, all processes and all sessions are checked.

I've tried explicitly setting all projects to x64 from AnyCPU, no change.

Yes, I'm running as Administrator.

When using Debugger.Launch() I get the following exception in Windows app log:

Log Name:      Application

Source:        VsJITDebugger

Date:          11/3/2009 12:08:03 PM

Event ID:      4096

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      *

Description:

An unhandled exception ('Launch for user') occurred in w3wp.exe [5916]. Just-In-Time debugging this exception failed with the following error: Not enough storage is available to complete this operation.

Check the documentation index for 'Just-in-time debugging, errors' for more information.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="VsJITDebugger" />

    <EventID Qualifiers="49152">4096</EventID>

    <Level>2</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2009-11-03T17:08:03.000000000Z" />

    <EventRecordID>3585</EventRecordID>

    <Channel>Application</Channel>

    <Computer>*</Computer>

    <Security />

  </System>

  <EventData>

    <Data>An unhandled exception ('Launch for user') occurred in w3wp.exe [5916]. Just-In-Time debugging this exception failed with the following error: Not enough storage is available to complete this operation.

Check the documentation index for 'Just-in-time debugging, errors' for more information.</Data>

    <Binary>0E000780</Binary>

  </EventData>

</Event>

Answer 1

Apparently one third-party open source project had a 32-bit dependency ... had to enable 32-bit on the app pool ... why doesn't the Configuration Manager, or the build process, alert you to this kind of conflict?