I did now. :)

That's in interesting approach, however it requires
that the name of the calling class be hardcoded into the
code in the child.

So, the only way that an instance of Child could be
returned is through ParentClass.GetChildClass, so no other
methods could return one.

However, all said, I do like it better than a public var.

Thanks



>>The best answer that I can come up with is thus far the public var idea.
>
>Did you see my example checking the stack? I think its cleaner than using variables as flags. You can check exactly that "the one trying to instantiate me is SuchClass.SuchMethod".
>
>Regards,