Can't debug?

Hi all,

I'm a very experienced VB.Net developer just starting to climb up the
ASP.Net learning curve. I followed a couple of the beginning "how to"
tutorials included with the MSDN docs, but I've run into a problem that I
can't figure out. When I run my simple ASP.Net web app under the debugger,
it doesn't stop at any breakpoints.

Here are the details: I'm using VS 2005 Team Suite SP1. I created the
solution by selecting "Create: Website" from the start page and selecting
the "ASP.Net Web Site" template. The first time I tried running under
debug, I got a polite message telling me that I needed to uncheck the
"Disable script debugging" setting in Internet Properties, which I did.
That made the message go away, but that didn't help. I've checked my
web.config file and it contains

<compilation debug="true" strict="true" explicit="true"/>

When I press F5, Visual Studio looks like its starting to run under debug,
but then my web page is displayed and breakpoints are simply ignored. (The
red ball next to the breakpoint is filled in, indicating that the debugger
is happy with that line. And I know it has to be executing that line
because I see the result on my web page.) Another strange behavior is that
the part of the VS text editor that was occluded by my web page when it was
displayed is not redrawn correctly, leading me to suspect that VS is somehow
unnaturally unhappy with something I'm doing.

Any suggestions?

TIA - Bob

The red ball next to the breakpoint is filled in, indicating that theOk, that's a red herring. When I press F5, the Visual Studio IDE changes as
though it is beginning to run under debug, but by the time my web page is
displayed the debugger appears to have terminated. That is, the IDE is
ready for me to resume editing, and the Debug->Run menu item is again
available. That's why the breakpoint is displayed as a solid red ball --
it's being displayed in "edit" mode, not in "debugger is running" mode.

But even though the IDE is back in "edit" mode, my web page is still being
displayed by the ASP.Net Development Server as though I had pressed ctrl-F5
rather than F5.

"Hongye Sun [MSFT]" wrote on 25 aug 2008 in
microsoft.public.inetserver.asp.general:
This is not the Microsoft Newsgroup Support Service but Usenet, Hongye.
And this NG is specialized in classic ASP,
so please do not use it for ASP.NET questions.

Misusing Usenet is detrimental to this NG and to the Microsoft name.

--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

I really thank you for correcting my fault, Evertjan.

This NG is specialized in classic ASP programming. And it is improper to
discuss ASP.NET here.

Hi Bob, in the future, for all ASP.NET issues, I would suggest posting in
the newsgroup below:

microsoft.public.dotnet.framework.aspnet

The reason why we recommend posting appropriately is you will get the most
qualified pool of respondents, and other partners who the newsgroups
regularly can either share their knowledge or learn from your interaction
with us. Thank you for your understanding.

After you create a new post, we can continue on your issue. Have a nice day.

Regards,
Hongye Sun (hongyes@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsoft.com.

This posting is provided "AS IS" with no warranties, and confers no rights.

This NG is specialized in classic ASP programming. And it is improper to
No problem...