loool Marius i understand your frastration,
Interfaces are used for two reasons
1. when you build a COM object you need the interfaces to be able to use the
code from other languages (ex vb6, c++, etc) that don't understant what the
hell a class is but the know interfaces.
2. if you build an interface for wrapping a database table, and add the
method save to it, then as many classes you have for the different tables in
your db, you only have to call Interface.Save();
so insdead of knowing in your code, what sort of table class you have to use
you treat the object as an interface and get rid of the if and buts of the
code.
Also by building interfaces you have a more efficient view of your model, if
you don't use UML to model your project before start writting any code.
P.S. If you do a change in the interface just go to the classes the
impliment it and add the implement again :
public class SomeCLass (: MyInterface) <-- delete this part and write it
again, and will build a region with the properties and methods that you just
add
hope that help
"Marius Horak" <no****@eu.con> wrote in message
news:eD**************@TK2MSFTNGP14.phx.gbl...
I've never used Interface and never will.
But now I have to make major modifications to a large system where
almost all classes are based on some kind of Interface. Hundreds of
classes.
When I want do add a new property or method I have to modify the
interface and next I have to modify dozens of other classes or create
new inteface.
Sooner or later I will finish having a single class based on its own
interface. So what is the point of using Interface?
Madness.
MH