F
Folke
Allow me to ask a really stupid question.
Why use interfaces in C# and .NET if you're not dealing
with hereditary COM+ components / clients.
I can see no benefit from it. Only complicates things.
Doesn't add code security. You still must get hold of
the .dll for the interface implementing class. They talk
of it as a 'Contract' and say that the implementing class
must implement the specific code. But contracts can be
broken - what if the class implements other public
methods? Nothing prevents you from doing that.
Why use interfaces in C# and .NET if you're not dealing
with hereditary COM+ components / clients.
I can see no benefit from it. Only complicates things.
Doesn't add code security. You still must get hold of
the .dll for the interface implementing class. They talk
of it as a 'Contract' and say that the implementing class
must implement the specific code. But contracts can be
broken - what if the class implements other public
methods? Nothing prevents you from doing that.