friend constructor

[Franz]

Class Foo has a private constructor. How can I give the right to Class Bar
to use that private constructor?
For example, the constructor of System.Windows.Forms.TreeNodeCollection is
private. How can the TreeView create an instance of TreeNodeCollection?

[Morten Wennevik]

Hi Franz,

You can give it access to a static method that will return a new instance of Foo

--
Happy coding!
Morten Wennevik [C# MVP]

[Franz]

"Morten Wennevik" <Mo************@hotmail.com> ¦b¶l¥ó
news:opr9momhsiklbvpo@morten_x.edunord ¤¤¼¶¼g...

Hi Franz,

You can give it access to a static method that will return a new instance of Foo

I have thought about it. But I just want Bar to be the only class which can
create an instance of Foo.
internal constructor is good. But it opens to all the class within the same
assembly.

[n!]

> I have thought about it. But I just want Bar to be the only class which
can

create an instance of Foo.
internal constructor is good. But it opens to all the class within the same assembly.

You can make Foo a private class of Bar, and have it implement a public
interface.

n!

[Franz]

You mean this?

public class Foo {
private class Bar : IBar {
void bar() { ........ }
}
}
interface IBar {
void bar();
}

"n!" <nf********@nomailplease.com> ¦b¶l¥ó
news:%2******************@TK2MSFTNGP11.phx.gbl ¤¤¼¶¼g...

I have thought about it. But I just want Bar to be the only class which

can

create an instance of Foo.
internal constructor is good. But it opens to all the class within the

same

assembly.

You can make Foo a private class of Bar, and have it implement a public
interface.

n!

[n!]

> public class Foo {

private class Bar : IBar {
void bar() { ........ }
}
}
interface IBar {
void bar();
}

Yep, of course you only need the public interface if you want it visible
outside of the containing class.

n!

[Simon Smith]

I used to worry about that sort of thing too, until one day I realised
that if I couldn't trust my own code (i.e. the code in the same assembly)
then I was doomed anyway.....
Simon Smith
simon dot s at ghytred dot com
http://www.ghytred.com/NewsLook - Usenet for Outlook

On 15 Jun 2004 10:24, "Franz" wrote:

"Morten Wennevik" <Mo************@hotmail.com> bl
news:opr9momhsiklbvpo@morten_x.edunord g...

Hi Franz,

You can give it access to a static method that will return a new instance

of Foo

I have thought about it. But I just want Bar to be the only class which can
create an instance of Foo.
internal constructor is good. But it opens to all the class within the same
assembly.