Allow instantiation internal but not external?

[Bruce]

Is there any way to define a class in such a way that it will allow
instantiation of the class internal to my project but not allow it when
the class is used via the resulting DLL of my project? In ActiveX this
can be done with the noncreatable keyword. How can this be done in .Net?

I tried making the constructor protected protected but that did not seem
to work.

[Steve Alpert]

C# has an "internal" keyword.

Bruce wrote:

Is there any way to define a class in such a way that it will allow
instantiation of the class internal to my project but not allow it when
the class is used via the resulting DLL of my project? In ActiveX this
can be done with the noncreatable keyword. How can this be done in .Net?

I tried making the constructor protected protected but that did not seem
to work.

/steveA

--
Steve Alpert
my email fgrir.nycreg @ tr.pbz is encrypted with ROT13 (www.rot13.org) and spaces

[Bruce]

Steve Alpert wrote:

C# has an "internal" keyword.

>
/steveA

Thanks,

I tried again and placing all of the constructors under "private public"
does indeed work. VB's Intellisense allows the new keyword to be used
but throws an error once used.
Bruce