...make sure that I've cought all of the exceptions that I can...
You say that as if you think it's a good thing to "catch them all". That's a common novice mistake, so I think it's worth pointing out that you should never catch exceptions unless you know why they're thrown and how to recover safely. Otherwise, catching them will only make your bugs harder to find and fix.
Owen,
I've only interacted with you on occasion, but your reputation for excellence precedes you.
I accept your criticism, as I am a novice... At .NET development, Visual LISP, even development concepts and programming altogether. It is only through the feedback and guidance of others, such as yourself, that I have been able to achieve the level of development acumen that I currently have (no matter how insufficient that may be).
To clarify my statement, I do not intend on writing a catch block for each and every exception possible for the various Methods being invoked (System.IO.File.Move(), or
this thread, as a couple of examples). Instead, I am attempting to (albeit perhaps insufficiently) avoid many possible exceptions through test expressions where possible.
But there are those, as in the latter example linked above, and in System.IO.File.Move() such as UnauthorizedAccessException that I simply cannot (or at least do not know how to) mitigate without catching, reporting to the user, and throwing.
Acknowledging that I have much to learn, doesn't quite make the point adequately.