VS2010 + IE8 Debugging Problems - Item Not Found

Question

I'm having trouble debugging with vs2010 and IE8, although I think the problem is more specific to IE8. When starting a debugging session 9 times out of 10, I will have the following problem. The IE tab talks about connecting .. - then after 5 seconds of waiting I will get an error in VS that is not found. Even when I click ok to reject the error, the connection still appears in the IE window ... Then I have to kill the IE process to close IE in order to try again. Sometimes I got lucky and it starts. But all this is so accidental, I do not know where to start. One thing that I noticed is that I always have 2 IE processes, although only one window is open. One has a small area of ​​100 thousand, I believe that this is some kind of assistant.

I am using a static port with an embedded WebDev server.

If anyone had similar problems, please let me know how you resolved it. It drives me crazy! thanks

Answer 1

This sounds like a problem with the restored tab. Go to the Internet Options tab (ALT, T, O), go to the "Advanced" tab, then "View" and uncheck the box "Enable automatic crash recovery . "

You can also try adding "localhost" as a trusted site or (worse :) disable "Protected Mode" for all zones on the "Security" tab (at least for debugging).

If this does not solve the problem, it may be an inaccessible port.

Disable all software firewalls, check netstat -a at the command line to make sure that the correct port is being listened. If it displays the port as listening, the only thing I can think of is the hosts file in the% systemroot% \ system32 \ drivers \ etc \ directory. Set "127.0.0.1 localhost" to split.

If the port is not listed as listening, this is a VS or service issue. This VS 2005 page should cover any related reasons .

Answer 2

I use a different approach. I will always run the application and then use VS to join this issue. Typically, the steps work as follows:

• Configure the application to work in IIS.
• Run VS as administrator or with administrator privileges. If you do not take this step, VS will inform you.
• Go directly to the problem.
• In VS Go to Debug → Attach to a process or use the CTRL + ALT + P hotkey
• If the problem is with server-side code, then attack w3wp.exe (make sure you are connecting to the correct w3wp.exe, you may have several, due to Classic / Pipeline). OR Attach to an instance of IE using the header specified in the title of your web page.
• If it is connected to the server, then VS will automatically break. If you are tied to IE, make sure you set the breakpoint in the correct position in VS.

Regardless, debugging IE using VS has always been very risky. IE8, built into the debugger, is usually up to the task.

An additional advantage of using this method is that it is faster to debug complex web applications, since you can usually leave the web application open near a problem place when restoring a site.

Answer 3

I will give you the key to several running IE processes: if you start IE8, you will get one host process and one worker process. When viewing the list of processes in the "Attach a process" window in VS, the host will display the page title, while the worker will not have a title. You want to attach to a workflow (one that does not have a name). This can be confusing, so in most cases avoid using multiple tabs when debugging, so you always have two processes.

Is the IE tab written with only "Connecting ..." to the debugger application or otherwise? You did not say anything about any breakpoints that might be active, and if that could affect the process, not moving forward.

Answer 4

Have you looked at the stack trace in Visual Studio to find out what doesn't work in Javascript? What element is not found and where is it from? What is expected?

I have had similar problems in the past, and sometimes this can be the result of poor javascript. Use the stack trace tab in your debugger to find out which item is not working. If you can activate an element in an object in the DOM or better yet, but your code, you can narrow down where the problem is.

Answer 5

I would debug this in Chrome. Built-in developer tools for debugging JavaScript are fantastic.

Answer 6

This may be a problem in the IE8 LCIE (Loosely Coupled Internet Explorer) process model. IE8 introduced the (poorly thought out) idea of ​​launching new IE processes when you open new browser tabs. You start with two instances of iexplore.exe in the task manager, and they quickly multiply by 8, 12 16 processes, etc., each of which captures a huge amount of memory and resources. VS2010 handles LCIE very poorly, with various and numerous problems. Best practice is to disable LCIE:

• Start-> Run
• Enter regedit
• Go to HKLM \ SOFTWARE \ Microsoft \ Internet Explorer \ Main
• Add a REG_DWORD key called TabProcGrowth
• Set the value to 0 (zero)
• Close all instances of IE.
• Close the VS2010 session.
• Try again.

Even if this does not solve your problem, it will fix all sorts of other problems. TBH I don’t see how anyone can debug VS2010 + IE without disabling LSIE.