M
Mario
It seems to me that a "time out" exception is a fairly routine
exception that can occur either when I'm reading from or updating to a
database. That said, it's a bit curious that there is no built-in
exception for trapping a time out.
Presently, I simply trap a vanilla SqlException and then I check the
start of the message for the "Timeout expired." text. If I find it, I
recast the exception using a "new TimeoutException(ex)". I defined
this custom exception myself.
Doesn't it seem practical that the .NET framework would include a
native exception such as TimeoutException or SqlTimeoutException? Why
should I and thousands of other programmer have to parse the message
text?
How are others handling time out exceptions? Am I missing something?
Mario T. Lanza
Clarity Information Architecture, Inc.
exception that can occur either when I'm reading from or updating to a
database. That said, it's a bit curious that there is no built-in
exception for trapping a time out.
Presently, I simply trap a vanilla SqlException and then I check the
start of the message for the "Timeout expired." text. If I find it, I
recast the exception using a "new TimeoutException(ex)". I defined
this custom exception myself.
Doesn't it seem practical that the .NET framework would include a
native exception such as TimeoutException or SqlTimeoutException? Why
should I and thousands of other programmer have to parse the message
text?
How are others handling time out exceptions? Am I missing something?
Mario T. Lanza
Clarity Information Architecture, Inc.