Why we can't use access modifier with interface method

Question

public interface Class1 { public void LoadData(); void UpdateData(); void IntializeData(); string Make { get; set; } } I want to know the reason please any one can help.

Abhineet Srivastava · Answer

Got it. Thanks

Vulpes · Answer

Here's an example which uses a private interface. You'd only use these in practice when you have a complex system of nested classes and you want some of them to implement the interface: using System; public class MyClass { private interface IFace { void MyMethod(); } public class MyNestedClass1 : IFace { public void MyMethod() { Console.WriteLine("Hello from MyNestedClass1"); } } public class MyNestedClass2 : IFace { public void MyMethod() { Console.WriteLine("Hello from MyNestedClass2"); } } } class Test { static void Main() { var mnc1 = new MyClass.MyNestedClass1(); mnc1.MyMethod(); var mnc2 = new MyClass.MyNestedClass2(); mnc2.MyMethod(); Console.ReadKey(); } }

Abhineet Srivastava · Answer

As per as I read, Interface only have Public modifier & Abstract class have any one of these modifier. Cheers

Abhineet Srivastava · Answer

Hiya Vulpes, One confusion-- What will the use of Interface with Private access modifier? Cheers

Vulpes · Answer

All members of an interface are implicitly public. Rather than insist on adding the public access modifier to every member, the C# design team evidently felt - in the interests of brevity - that it was better not to allow any access modifiers at all. Note though that the interface itself can have any of the access modifiers : public, internal, protected, protected internal or private. If no access modifier is specified, a 'top level 'interface is internal and a 'nested' interface is private by default.

Abhineet Srivastava · Answer

Interface is a about to be global i.e, can be access anywhere from programme so it always be public.