Well, the most important thing in programming an interface is that it allows you to exchange certain classes while new classes implement everything in that interface.
eg. I program my dataSource object on an interface, so I can change it between the xml reader and the sql database reader.
Does this mean that every class must be programmed into an interface? When is it not recommended to use the interface?
When does the YAGNI principle apply.
, , , , . , , .
. , , . , , - .
, , . , , , , , IComponent , .
, . , , .
, . , ( #, ), , REAL.
, , DTO, , , , , .
, , ; , (, hehe), , , , .
, , , . , , , , ICustomer. , s.a. " ", , , ISavable.
- . , ypu SMS-, SMS , , , s.a. ISmsGatewayAdapter, , .
"dependecy injection",
: ? , - .NET, ! .
, - , , .
, " ?" . . , , , , , , .
. , , StructureMap, "... IWidget", . , , , . , , , , , , .. , . , , . SOLID-, .
, , , . Err .
YAGNI.
Visual Studio, , ( ). .
, . , .