Since Microsoft published IE8 as a Windows Update and my boss said he upgraded to it, I figured it was safe to upgrade to it as well. I’ve been enjoying the changes for a couple days now, but when I attempted to debug an ASP.NET application with Visual Studio 2005, it would no longer stop at a breakpoint. Pretty frustrating if you ask me. I’ve found a few articles online describing problems, most of which I haven’t encountered yet. You may want to implement all these workarounds.
- Some VS2005 and VS2008 Wizards Pop Up Script Error
- VS 2005 Debugger crashing with IE 8 Beta 2
- Why can’t I debug from Visual Studio 2005 after installing IE8?
- Script debugging broken in VS 2005 after installing IE8
- Debugging with VS 2005 and IE 8
The problem I was having appears to be related to how IE8 uses multiple processes. Apparently VS 2005 doesn’t know which process to attach to. Here are three solutions:
- Don’t have IE8 running at the time you want to debug. This worked for me.
- Modify the registry as described in the second link above. This worked for me as well. Here are the steps:
- Open RegEdit
- Browse to
- Add a DWORD value called
TabProcGrowthwith a value of 0
- Turn off protected mode browsing in IE (Security page of Internet Options) if you are running on Vista or newer.
- Uninstall IE8 to revert back to IE7. I don’t really want to do this though. I’ve grown particularly fond of a few of the new features in IE8, such as previous session restore (although I wish it would allow me to restore more than just the last session) and improvements in search.
I don’t know if this is a problem with VS 2008, but some of the articles seem to imply it only applies to VS 2005. Maybe it’s time to upgrade Visual Studio