I\'m looking at the article C# - Data Transfer Object on serializable DTOs.
The article includes this piece of code:
public static string Se
It depends what you are doing in the catch block, and if you are wanting to pass the error on to the calling code or not.
You might say Catch io.FileNotFoundExeption ex
and then use an alternative file path or some such, but still throw the error on.
Also doing Throw
instead of Throw Ex
allows you to keep the full stack trace. Throw ex restarts the stack trace from the throw statement (I hope that makes sense).