I'm in asp.net 1.1 hell....re debugging and breakpoints.
- From: "Randy Magruder" <randy.magruder@xxxxxxxxx>
- Date: Mon, 30 Oct 2006 16:59:52 -0800
Attn: Asp.net gurus...if anyone can help, I hope it's here.
Okay, I'm at my wits end. I have googled til my fingers hurt and am
still not finding answers.
The symptoms are as follows:
1. I have 2 machines, my laptop and a desktop, both are set up for
asp.net development.
2. The desktop machine has an asp.net 1.1 app written with vs.net
2003. It is written in vb.net and runs and debugs properly
3. The laptop also will debug the vb.net 1.1 app
4. Both machines will also debug a C# asp.net 1.1 app with no problems.
5. Converted the vb.net app to C#. Can't get a page_load breakpoint
on the main.aspx to EVER stop.
- All the debug checklist items I can find are taken care of
a. Projects are built in debug mode
b. All the Web Site properties seem to be set properly for
asp.net debugging,
c. I belong to the debugger users group
d. I've deleted all the 'extra' copies of dll's lying around,
purged the temporary asp.net files cache, etc.
e. Again, remember that simple hello world c# apps along with
the large vb.net ALL debug, so the machines seem to be configured
correctly.
f. the web.configs are properly configured with debug= true
Nonetheless, no breakpoints get hit in the Page_load of the main.aspx
that loads. It just goes right through it and redirects to login.aspx,
whose breakpoints on Page_Load are ALSO ignored.
There are no question marks in the breakpoint margins or any other
indication that symbols are missing or not loaded. The binaries are up
to date. Every freaking thing I can find on google or msdn or anywhere
seems to tell me that the debugger should stop just fine. But instead
it just whizzes right through the code.
It can't be the language, as it stops in page_load of simple 'demo' C#
asp.net apps
It can't be the machine, as both debug vb.net and 'simple' C# asp.net
apps just fine.
It can't be cached dll's built with release info, as I deleted all the
dll's I could find (in both my documents and below, and in the
temporary asp.net directories....
It can't be web.config, as it is identical to those projects that DO
debug.
It can't be machine.config, as obviously other apps on the same machine
DO debug.
It can't be vs.net, as I've tested all this stuff on both Vs.net 2003
and bds2006.
It can't be multiple versions of asp.net, as I removed asp.net 2.0 from
my machine to eliminate any confusion.
It can't be re-starting IIS or re-running aspnet_regiis, as I've run
that til I'm blue in the face.
It can't be a debug='false' in the page header, as those are not there.
It can't be re-installing IIS as I've done that.
Can someone with a degree in the black art of asp.net tell me something
that I have NOT tried? It's killing me here that no breakpoints EVER
get hit here...and yet I can debug 'simple' apps with no problem.
Thanks to anyone who has an idea what piece of obscure asp.net trivia
I've missed.
Randy
--
.
- Prev by Date: redirect missing php page to aspx page - CustomErrors won't work?
- Next by Date: Re: can I force Page.IsPostBack=false ?
- Previous by thread: redirect missing php page to aspx page - CustomErrors won't work?
- Next by thread: How have apostrophe (single quote) show up?
- Index(es):
Relevant Pages
|
