Why would the debugger not be stopping at a breakpoint in my ASP.NET application?
People.... I found other solution for breakpoint dont stop.In Attach to Process window on Visual Studio 2010 and using Framework 3.5, by default automatically determines the code types to debug (v2.0, v1.1, v1.0) and (v4.0).
Visual Studio gets confused and automatically determines 2.0 managed code as 4.0 managed code sometimes.
In this case you need to click in "Select..." button on "Attach to" field and select Manage (v2.0, v1.1, v1.0).
Regards
VS Debug Problem with IE8
Since this is my first post on Weblogs, I decided to write about a problem that has been opened frequently on the ASP.NET official forum which is the VS debugger crashes with IE8.
I had answered the same problem 4 times, so I hope that some one will find this post very helpful if he is facing the same problem.
How could the VS debugger crash with IE8?
If you opened multiple instances of IE8 and you attempt to debug your project, you will mostly have the issue where the VS debugger just stops and ignores your break points!
Why was that?
IE 8 has a feature called Loosely-Coupled Internet Explorer (LCIE) which results in IE running across multiple processes.http://www.microsoft.com/windows/internet-explorer/beta/readiness/developers-existing.aspx#lcie
Older versions of the Visual Studio Debugger get confused by this and cannot figure out how to attach to the correct process.
To overcome this issue, you need to disable the process growth feature of LCIE by following the below steps:
1) Open RegEdit2) Browse to HKEY_LOCALMACHINE -> SOFTWARE -> Microsoft -> Internet Explorer -> Main3) Add a dword under this key called TabProcGrowth4) Set TabProcGrowth to 0
If you run into the same problem on Vista or newer, you will also need to turn off protected mode.
And then go ahead and start debugging your code :)