You should not access private members in the derived class. This is what private access was designed for: to prevent access from anywhere except the declaring class itself. To make a member accessible from a derived class, you should give it any access specifier except
private
: it could be either
protected
,
protected internal
,
internal
or
public
. Note that it's important to give only the minimal required access, no more.
If you really want to abuse these access rules (in some really rare cases this is really useful),
reflection is at your service. That said, access specifiers are only to protect a developer from himself, not a security device. I'm not sure if reflection is relevant to your question (most likely, it is not), so you can learn about it by yourself or ask your follow-up questions if you have to:
http://en.wikipedia.org/wiki/Reflection_%28computer_programming%29[
^],
http://msdn.microsoft.com/en-us/library/f7ykdhsy.aspx[
^],
http://msdn.microsoft.com/en-us/library/system.reflection.aspx[
^].
—SA