M
Marian Edu
Guest
don't see anything wrong with that, I would just skip the setter on the property as that it's just a proxy to the private variable keeping the actual reference using a private variable to keep the reference is mostly just to avoid useless object creation on destructor if it happens not to be instantiated by that time as will happen in Tim version, aka create something when actually trying to clean-up. other than that I've never seen a behavior where properties are evaluated on constructor unless some piece of code fired by the constructor will access those properties so you better check out what is happening in those constructors, your class and base class(es)
Continue reading...
Continue reading...