M
Mike Hofer
In my ASP.NET application, *one* page would not render in the
application. All others would show up just fine, but when the user
clicked the button to browse to this one page, I'd get a nasty error
message from IE: "Cannot find server or DNS error."
I set some break points and determined that the page was being loaded,
but that the error page was being displayed anyway. Fortunately, I'm
pretty obsessive about logging errors (both in my database and in the
event log). A little research revealed that I had changed the names of
a couple of controls and hand't updated their validators accordingly.
ASP.NET doesn't bind validators to their target controls until runtime,
which is kind of annoying. If the controls don't exist, you'll get that
spiffy error message I described above.
So double-check your ControlToValidate and ControlToCompare properties.
I hope this saves someone lots of frustration.
Happy coding.
application. All others would show up just fine, but when the user
clicked the button to browse to this one page, I'd get a nasty error
message from IE: "Cannot find server or DNS error."
I set some break points and determined that the page was being loaded,
but that the error page was being displayed anyway. Fortunately, I'm
pretty obsessive about logging errors (both in my database and in the
event log). A little research revealed that I had changed the names of
a couple of controls and hand't updated their validators accordingly.
ASP.NET doesn't bind validators to their target controls until runtime,
which is kind of annoying. If the controls don't exist, you'll get that
spiffy error message I described above.
So double-check your ControlToValidate and ControlToCompare properties.
I hope this saves someone lots of frustration.
Happy coding.