Interface members accesibility

[Heinz_]

Hi, Methods in an interface must be public? If i have a public method in an interface, can i make this method "internal" (or any other access parameter) in a class derived from the interface? ie: public interface myinter { public void MyMethod(){} } public class myclass : myinter { internal void MyMethod(){//my code} }

[Colin Angus Mackay]

Heinz Suez wrote: Methods in an interface must be public? Yes, that is the point. It is defining the external interface* to something. In other words, it is defining the interface* (or part of the interface*) to your class that other classes use. Heinz Suez wrote: If i have a public method in an interface, can i make this method "internal" (or any other access parameter) in a class derived from the interface? No. You cannot. This is because the class would then no longer support the interface it advertises as supporting. Do not confuse "interface" with the C# keyword "interface". An interface is another way of saying how an external entity sees the class. You provide an interface with any public methods. An interface is a way of defining a common set of public methods or properties that a number of classes support.

---

My: Blog | Photos "Man who stand on hill with mouth open will wait long time for roast duck to drop in." -- Confucious

[Robert Rohde]

First of all your code won't compile :) And yes all members of an interface must be public visible to everyone using this interface. But you can restrict them ONLY to explicit interface users:

public interface ITest
{
void TestA();
}

public class Class1 : ITest
{
void ITest.TestA() {}
}

static void Main()
{
Class1 c = new Class1();
c.TestA(); //gives compile error
ITest t = c;
t.TestA(); //works perfectly well
}