>>>

>>>Test.MyObject mo = (Test.MyObject)Activator.CreateInstance(typeof(Test.MyObject),true);
>>>

>>
>>If developers can create the object using reflection then it defeats what I'm trying to achieve anyway. (I was assuming I could prevent this by setting ReflectionPermissions - but I have'nt tried it yet...)
>>
>>Best,
>>Viv
>
>Yes, it might be. On general it'd be too much complicated to control it. Basically what I'm doing is, just prevent direct creation (they could use reflection - actually 'they' is me and easier to control, a reminder to use factory methods instead:).

I think your right. I'm not up to speed on reflection in NET2 but it seems to me that if I allow reflection on private types then anyone else can also use it to directly create the object (this circumventing my intention).
My brain is begining to hurt :-(
Viv