Working around the lack of friend classes

[matt cole]

Hi, I have a situation where I have a class which I would like to be visible within its assembly, but only to be able to be created by a single other class. Ideally I would make the constructor private and the other class a friend and this would solve the problem, but that's not possible in c#. I was hoping there may be some special property of a nested class to allow this but it doesn't seem so. Can anyone think of another way to do this? Thanks, Matt

[Christian Graus]

There is no clean way. C# sucks.

Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog

[Judah Gabriel Himango]

Christian Graus wrote:

There is no clean way. C# sucks.

;P Aww man...come on now. I come from a C++ and Java background; to me, C# rocks. :)

Tech, life, family, faith: Give me a visit. I'm currently blogging about: God-as-Judge, God-as-Forgiver The apostle Paul, modernly speaking: Epistles of Paul Judah Himango

[Leslie Sanford]

matt cole wrote:

I have a situation where I have a class which I would like to be visible within its assembly, but only to be able to be created by a single other class.

Create an interface representing the functionality of the first class. Have the first class implement that functionality as a private class to the second class:

public interface ISomeInterface
{
void DoSomething();
}

public class MyClass
{
private class MyPrivateClass : ISomeInterface
{
public void DoSomething()
{
// Do stuff here...
}
}

public ISomeInterface Create();
{
    return new MyPrivateClass();
}

}

Maybe not exactly what you're looking for; you have the interface in your namespace which may not be implemented any where else, but that may not be a problem.