Does any one has a better ideal of handling error with try..catch for the
following scenario.
1. the process could cause many kinds of error. which means the nested
try..catch may happen.
2. Regardless of error occor or not, the process hould end up to release
memory by setting the object variables to nothing.
3. the process of method is in class of some kind of dll. So, when system
got error, it raise error.
4. I don't want to put the setting object variables to nothing code to every
catch procedure, it is awful.
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.