On 'crash-proofing' ASP.Net 2.0 code

  • Thread starter Thread starter B. Chernick
  • Start date Start date
B

B. Chernick

This is related to an earlier post of mine. In a general sense, how does one
'crash-proof' 2.0 webpages, especially when dealing with legacy databases?
To be more specific, Visual Studio 2005 and ASP seem to be extremely
unforgiving of bad or null data, especially datetime fields and bad values
that are intended to set dropdown list indices.

Short of manually writing binding code, is there any way to deal with
problems like this?
 
Actually no, user input I can deal with.

What I was thinking of was massive legacy databases full of questionable or
non-existent data integrity (and either too big to cleanup overnight or
politically off-limits), as well as wannabe DBAs going into tables directly
and modifying data, just to make my life even more interesting than it
already is.

It just seems vastly easier to handle this sort of thing in Winforms.
 
Back
Top