C#DotNet: When to use Interface

Monday, September 12, 2011

When to use Interface

If the requirement is like that something in your design changes frequently then go for interfaces instead of classes .

read more

No comments:

Post a Comment

Do you know?

Private class members are inheritable to the base class, but will not be able to access them

RPC,Webservices,REST are principles , they do not belong to any languages .NET, Java,..

The CLR provides the appearance of an application virtual machine so that programers need not consider the capabilities of specific CPU that will execute the program

Static Members and Classes cannot be accessed by instance of a Class (i.e by an object)

DLL's don't get loaded in RAM together with the program , so space is saved in RAM(Random Access Memory)

Interfaces cannot have access modifiers such as public/private..

C# doesn't support Constant Methods,Properties or Events

C# doesn't support multiple inheritance , but by interface.

C# compiler doesn't allow use of uninitialized variable

C#DotNet

Monday, September 12, 2011

When to use Interface

No comments:

Post a Comment

Popular Posts

Wikipedia

Labels