views:

22

answers:

2

There is this one action that is requested using javascript during the loading of a page, it takes over 25 seconds to resolve. Looking at the code makes me think there is a scaling issue, but I am wondering if there is any way I can step through the code during the request so I can see what is happening. I try clicking 'debug/start debugging' but it won't launch the proper URL (access to the site is subdomain based), and it will also not find certain dependencies. I am able to browse the site directly via URL locally after mapping a URL via my hosts file to localhost (127...) but the default url that pops up (localhost...) from debug does not work because it is not formatted properly.

Any ideas?

A: 

You can attach the debugger to your browser by selecting "Attach to process" under "Debug" menu.

Rahul
it's not gonna help if the app is on a remote server, and you don't attach to the browser, you attach to the w3wp IIS process
Omu
"No symbols are loaded for any call stack frame. The source code cannot be displayed." when I click Pause, how to inspect?
shogun
@Omu - can't seem to find this process
shogun
@Ryan if the app is not hosted on your computer than there is no way you could find it
Omu
The app is most definitely hosted on my computer, just like my question states: "...in IIS locally after mapping a URL via my hosts file to localhost";
shogun
A: 

In the past, at least with ASP.NET we have used tracing to debug issues. You will just need to enable it in the webconfig. If you use warn, the messages will show in red and be easier to spot.

Josh