Enforce that a class can only inherit one interface

[Niklas]

Hi

Is it possible in one way or another to enforce that a class only inherit
from one of the derived interfaces of a base interface of some kind. For
example.
public class MyClass2 : IMyInterface1 => OK
public class MyClass2 : IMyInterface1, IMyInterface2 => Error

Regards
/Niklas

public interface IMyInterfacsBas e
{
string MyMethod1();
}

public interface IMyInterface1 : IMyInterfacsBas e
{
int MyInt1{ get; }
}

public interface IMyInterface2 : IMyInterfacsBas e
{
int MyInt1{ get;}
int MyInt2{ get;}
}

public class MyClass2 : IMyInterface1, IMyInterface2
{
private int _MyInt1 = 4;
private int _MyInt2 = 5;

public int MyInt1
{
get { return _MyInt1; }
}

public int MyInt2
{
get { return _MyInt2; }
}

public string MyMethod1()
{
throw new NotImplementedE xception();
}
}

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

"Niklas" <Ni****@discuss ions.microsoft. com> wrote in message
news:5A******** *************** ***********@mic rosoft.com...

Hi

Is it possible in one way or another to enforce that a class only inherit
from one of the derived interfaces of a base interface of some kind. For

First of all, a class do not inherit an interface, it implement it. which is
different.

And no, there is no way I know of to especify that a class can implement at
the most one nterface.

If you substitute interface by class you can be sure of that, as C# ins a
single inheritance language.

why you want to do this anyway?

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

[Joanna Carter [TeamB]]

"Niklas" <Ni****@discuss ions.microsoft. com> a écrit dans le message de news:
5A************* *************** **...icrosof t.com...

| Is it possible in one way or another to enforce that a class only inherit
| from one of the derived interfaces of a base interface of some kind. For
| example.
| public class MyClass2 : IMyInterface1 => OK
| public class MyClass2 : IMyInterface1, IMyInterface2 => Error

No, but you can delegate an interface to an aggregated object inside the
main class, so that each interface's behaviour is looked after separately,
even though the class implements more than one interface.

What are you really trying to achieve ?

Joanna

--
Joanna Carter [TeamB]
Consultant Software Engineer