Try Catch...need my brain rattled.

[darrel]

Trying to get back into .net again after being out of it for a while.

I'm trying to figure out the proper way to handle multiple events via a try
catch.

What I'm confused about is the proper method to handle, say, 3 separate
events: A, B, and C. I only want all 3 to execute if all 3 can successfully
execute.

Is that what a try-catch is for, or is a try/catch mainly for individual
events?

Is there a best-practice way to handle checking for 3 separate events and
only executing all 3 only if they all can execute without error?

-Darrel

[darrel]

What do these functions actually do?

Well my real world example was a file system update + a DB update. In
reality, the try-catch will be fine, as if the DB fails then the page likely
isn't loading at all, so I can mainly just check for the file system
function in the try-catch. If it fails, the DB update doesn't happen.

But then that got be thinking hypothetically of exactly what you decribe:

It sounds like what you are after is a transactional system whereby the
effects of A, B and C must only be commited if all three are successful.

Indeed, at that point, hopefully I'd be doing everything within SQL and
leverage transactions.

Otherwise, as Goran states, I write a bunch of code. ;o)

-Darrel

[darrel]

You can't do that using merely a try...catch. You either need a way to
tell if a method will be able to execute before actually executing it,
or a way to rollback the method.

Thanks! That confirms my line of thinking!

_Darrel