Interface Design : Hiding Members

[DIMPLE_R]

I have an Interface say InterfaceA which has two method declarations Method A & Method B The above interface is implemented by Class X Additionally Class X also has two more methods Method C & Method D If I instantiate an object of Class X, I want only Method C and Method D to be exposed. The Method A and Method B should not be exposed by default to the user unless he explicitly casts it..How do I design such an interface and how will the user do the 'casting' if required If anybody knows how to do this..pls help Dimple

[minhpc_bk]

public interface IInterfaceA
{
void MethodA();
void MethodB();
}

public class X : IInterfaceA
{
void IInterfaceA.MethodA() { }
void IInterfaceA.MethodB() { }

public void MethodC() { }
public void MethodD(){}

}

Explicit Interface Implementation[^]

[DIMPLE_R]

Hi, Thanx for the info...But I was trying to implement this with VB.Net..Saw a few posts on the topic..Was wondering why this feature has been highlighted as an advantage point in C#...Can i not do the same in VB.Net? Dimple

[Paddy Boyd]

Could you just do this: interface A { Method A Method B } interface B { Method C Method D } Class X: Interface A, Interface B { ... etc. } And then have user only instantiate one of type a or type b.

[minhpc_bk]

Hmm, I'm not a true VBer :), but you might think of hidding the interface's methods in the implementation class with the low access level like private or protected:

Public Interface IInterfaceA
Sub MethodA()
Sub MethodB()
End Interface

Public Class X
Implements IInterfaceA

Private Sub MethodA() Implements IInterfaceA.MethodA
End Sub
Protected Sub MethodB() Implements IInterfaceA.MethodB
End Sub
       
Public Sub MethodC()
End Sub
Public Sub MethodD()
End Sub

End Class

Btw, for this kind of question, you might want to ask in the VB.NET forum.

[DIMPLE_R]

thanks minhpc_bk