It's possible, but you'll need to write your own custom permission and
attribute to do this, which is probably a bit more work than you might have
been expecting. Is there some reason that making ClassA a private nested
class within ClassB wouldn't be an acceptable alternative? (Either way,
highly privileged code will be able to bypass the protective mechanism, but
both approaches will allow protection against most partially trusted code.)
"Robert Zurer" <ro****@zurer.com> wrote in message
news:MP************************@msnews.microsoft.c om...
I am new to CAS and sould like to know if it is possible to do the
following:
I would like to attribute properties and methods ClassA so that they may
only
be called by ClassB otherwise an error will be thrown.
If this is not something CAS can do, I'll go to plan B. If so, I would
appreciate someone suggesting pointing me to a good article or book.
Thanks in advance
Robert Zurer