Well then, I may just get a bit lazy.

Is there ever a time in .NET when you cannot have something throw an error? You could put a Try...Catch within a Catch block to trap an error, but is there a place where you can't live with an error?

It seems like the problems with constructors throwing errors that exist in C++ would also apply to VB.NET. Should you utterly avoid having the sub New raise an error?