I've looked in tools | options but there is no debugger choice, even with "Show All Settings" checked.  My choices within Options are Environment, Projects & Solutions, Text Editor, Database Tools and HTML Designer.  Is turning this off available in Express?

Try setting

 HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\Debugger

JustMyCode, DWORD, 0

Actually

HKEY_CURRENT_USER\Software\Microsoft\VWDExpress\8.0\Debugger

Thanks guys, but what do I do with this string?  Where does it get input or inserted?  Sorry to be a newbie.

That's a registry key. JustMyCode is a value under the key, type DWORD, value 0. Use RegEdit.

I am not sure though why do you need to switch it off. Switching off JustMyCode does not give you much in ASP.NET debugging, there is not much to see besides code in the form. 

Mikhail,

I may be grasping at straws, but I'm having an on-again, off-again problem where the local version of my website won't run locally, even though it is an exact duplicate of the version that is running successfully on my live server.  My website is the front-end to a back end database system, and I believe (I'm guessing) the reason it won't run (by that I mean it just returns my standard error page, not the server error page) is that it is not connecting to the backend database.  I had this problem ten days ago for five days straight, and then suddenly it cleared up and worked fine for the next 3-4 days. 

 When I tried to do some debugging (though admittedly I don't know what I'm doing) I got a message associated with the first identified issue that said it couldn't do something because "Just My Code" debugger option was "on".  I thought perhaps this meant it was only running my code and maybe not the code or the connections that are needed to access the backend database, in which case it returns the error message.  Does that make sense to you, or does it mean/do something else?  There's an SDK embedded in my site that comes from the back end data folks.  I thought perhaps it was ignoring that in just my code mode, which would prevent it from working.

 Other than this as a possible fix I'm stumped - I've tried disabling all firewall and norton items, I've tried doing an uninstall and re-install of VWD, but none of them seemed to fix it the  first time (when it just suddenly worked) or this time I expect.

 

Jeff

Oh, no, Just My Code only controls what debugger shows to you. It does not in any way controls which code is getting executed. When the setting is on, debugger hides from callstack those modules that are not part of the project you are working on. I.e you won't see, say, methods in System.Web, but they are still getting executed.

Maybe it is just network latency. When backend server appears to be down, can you still ping it? Does it reply and that is the reply time?

Mikhail, thank you again for your wonderful help.  I pinged the server which hosts my site, which is at the same physical location as the backend database and the round trip time for 32 bytes was 61 milliseconds.   I'm going to try to find the IP for the backend and ping it, but I assume it will be close to the 61 figure.  Is that high enough for latency concerns?

Mikhail,

 When I run in debug mode, I get an error that points to the "authentication mode" line at the very end of my web.config:

</pages>
<authentication mode="Windows"/>
</system.web>
</configuration>

 The error is:

Error 139 It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.  This error can be caused by a virtual directory not being configured as an application in IIS. C:\Documents and Settings\Administrator\Desktop\httpdocs\live\web.config 157 

When I learn a little about IIS directories it tells me: A virtual directory appears to client browsers as though it were contained in a Web server's root directory, even though it can physically reside somewhere else. This approach enables you to publish Web content that is not located under the root folder on your Web server, such as content that is located on a remote computer.

Maybe this is at the root of my problem in connecting to the backend database?  Any thoughts on that before I try to create one?

Hi Mikhail - the main reason to turn off Just My Code is that you can't debug into the .NET Libraries without it.  This is hugely frustrating-- I sometimes end up having to toggle Just My Code several times during a debug session, or (more commonly) end up with Just My Code turned off from a previous session where I needed to look into the .NET Framework library source.  Suddenly ASP.NET Exception debugging stops working.

Please do what you can to fix this in a later release of ASP.NET so you can debug into the .NET Source *and* catch exceptions in ASP.NET debugging!