Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Dec 28, 2006 05:25 AM|LINK
Thank you, Scott. You've been great and I really appreciate your help. I'm far less frustrated now. :-)
Yes, web.config can be frustrating and hard to debug. It's often just the case of knowing what to try and what can go wrong.
I've been thinking a lot lately about how Microsoft could improve things. One thing would be to provide a web.config validator/debugger. The former would be an option at debug time to scan the web.config for errors and report the problems, and the second
would allow you to set "alert points" that alert you when they are not run.
For the Page_Load problem, I noticed you have AutoEventWireup="false" in the @ Page directive. This means you'll have to wire up the event handlers manually, which might be what you are missing. I have a post on this topic:
It's so obvious, now that you mention it! :-( Doh! But similarly, it would be great if Visual Studio would sent that I have a breakpoint in a function that won't be run because of AutoEventWireup and instead put up a warning telling me what I need to do
to fix it. Doesn't that sounds like a good idea to get more newbies productive with Microsoft technologies (as opposed to them moving to Linux technlogies?)
Yes, wildcard application maps are possible on XP.
Any guidance on how to set it? It's not available within the MMC dialog.
Wildcard Application Maps
Page_Load not firing