Last post Aug 10, 2009 10:26 AM by desertfoxaz
Aug 07, 2009 01:21 PM|desertfoxaz|LINK
I have to maintain some legacy applications that were created by VS2003. This week, the debugger stopped working for all of my projects. None of the project settings changed, and ASP.NET debugging is still enabled in the project properties and debug mode
is selected for builds.
I can create a new web project and place the breakpoint on the Page_Load event handler and when I click the play button on the toolbar it becomes disabled until the page loads then once that's done, the play button enables again.
I didn't do anything to my workstation aside from reinstalling the MSDN Library (which disappeared after installing the Oracle Data Provider), but perhaps our IT group installed something after business hours that may have affected something.
Has anybody experienced this before, and if so how did you fix it?
Aug 09, 2009 07:28 AM|aboobacker|LINK
I too faced the same issue,
did u installed IE8.. then
Well, IE 8 has a feature called Loosely-Coupled Internet Explorer (LCIE) which results in IE running across multiple processes.
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 follow the below steps:
1) Open RegEdit
2) Browse to HKEY_LOCALMACHINE -> SOFTWARE -> Microsoft -> Internet Explorer -> Main
3) Add a dword under this key called TabProcGrowth
4) 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 a head and start debugging your code :)
If you find this post useful Mark it as Answer
Aug 10, 2009 10:26 AM|desertfoxaz|LINK
Thank you so much! That did it. I was concerned that my VS2003 install was corrupted. I installed IE8 several weeks ago but hadn't tried debugging a .NET 1.1 app since before that.
You saved me a lot of grief. Thanks again.