G
George Addison
Every now and again, I make a mistake in ASP.Net code
causing an absolute catastrophe when it is encountered by
a browser. The site stalls, and even the FTP is
inaccessible--it freezes my browser so bad that I have to
kill the IE process! Luckily, I'm able to get to the web
files via an online control panel, but find that the bin
directory is locked, and I can't open it, or delete it
because it is being used by some iis process. This
continues for about a half hour. Yes, you heard it right-
-my site is bogus for a half hour!
(1) How can I avoid the site freezing up like it does
(global exception handler or something?);
(2) Isn't the compiler supposed to catch code bugs on
build?
causing an absolute catastrophe when it is encountered by
a browser. The site stalls, and even the FTP is
inaccessible--it freezes my browser so bad that I have to
kill the IE process! Luckily, I'm able to get to the web
files via an online control panel, but find that the bin
directory is locked, and I can't open it, or delete it
because it is being used by some iis process. This
continues for about a half hour. Yes, you heard it right-
-my site is bogus for a half hour!
(1) How can I avoid the site freezing up like it does
(global exception handler or something?);
(2) Isn't the compiler supposed to catch code bugs on
build?