I wonder what general strategy one should have when it comes to error handling in constructors. How do you do? Do whatever you can to avoid that it happens, that is only call the constructor with working range values.
Or do you throw exceptions and have a thorough handling of that.
I'm hesitating abit on how to approach it.
In general it's ok to throw exceptions from the constructor, several of the standard .NET classes does it.
You may want to be careful that you always release unamanged resources you have allocated though in case of an exception.
MagosX.com
Give a man a fish and you feed him for a day.
Teach a man to fish and you feed him for a lifetime.
Thanks
It is good practice to use error handling in constructors for anything and everything as you can not ensure the integrity of a resource. This prevents your system from crashing if a bad or poorly designed resource is opened with your application.
Excellent question.
