About unusual processing

I see MSDN, the code that there is unusual processing a little inside it a lot of Try paragraph very long, catch, finally.
This appearance is not Try paragraph in case make mistake, did not carry out from the back, receive Catch continuously, whole process function was not finished. I want to should be in the place that makes mistake the most easily to add Try.

Everybody will be solved. Join Try nature to affect efficiency, but always should have wrong and unusual processing -- unless you feel,the program won't have a problem really.

Have wrong processing of overall situation, also have local. . .
This appearance is not Try paragraph in case make mistake, did not carry out from the back, receive Catch continuously, whole process function was not finished. I want to should be in the place that makes mistake the most easily to add Try.

--------------------------------------------
If the program made mistake, should jump out of course. This is being added in the place that makes mistake the most easily is good. But you ensure. The program won't have a problem really. Try encounters wrong and unusual him meeting to jump to Catch, did not have those who carry out to won't be carried out again, of course, can carry out in Finally anyhow, unless Return is encountered before herKnew