||Understanding Interfaces in .NET|
Response to: interface naming
I think it is a matter of feeling:
If you handle an object and you write code
you feel different, if you handle objects of any type IXxxxx or if you handle objects of the type Xxxx. You always know that you dont really got an
object of the type IXxxx. You only got an object, which ALSO can do the things of IXxxx. It is sometimes really different if you just have a inherited class type object or a interface TO an object. If you dont FEEL right you wont CODE right. Of course your tool can tell you, if you have an interfaced or an inherited object. But this is only implicit. The explicit way is to use IXxxxx.