Comments on: Introduction to Interfaces in VB.NET

By: Lakshmi

Lakshmi — Tue, 27 Oct 2009 05:04:33 +0000

can u explain why we need to go for interfaces rather than calling a method.. Let me know whats the difference…

By: AnonNoob

AnonNoob — Mon, 07 Sep 2009 17:34:50 +0000

I think the whole point of interfaces is to implement ‘good code practise’, nothing more.

You use it to bind objects using an interface to a class, so you know 10 years later, which properties you have to construct or use. It is just a contractual aspect for coding.

That’s my take on it anyway.

You could be lazy (like me) and just use class properties and public / private methods to expose the parts you want other parts of the projects you want access to.

By: Mohsin

Mohsin — Mon, 15 Jun 2009 10:26:36 +0000

Well, all that was good, helpfull stuff about interfaces.
Got so much out of it, but still not feeling confortable saying that i have understood interfaces completely.

By: mukund

mukund — Tue, 02 Jun 2009 08:31:24 +0000

I am confusing to use interfaces.I want to know exact use of interfaces.My problem is:
W e can directly write methods in class instead of using interface.Then what is need of interface.

If anyone knows pls email me:

mukundguttal@rediffmail.com

By: confused

confused — Sat, 30 May 2009 12:19:38 +0000

What I don’t understand is implementing the ICOMPARABLE of .NET. Why do we need to use CompareTo method? Why can’t we create our own method to compare values? If there is no code in interfaces, what’s the use?

By: coby

coby — Wed, 13 May 2009 16:49:38 +0000

When you talk about interfaces you must remember that inheritance and implementation are two different things.
Interfaces are implemented where classes are inherited.

Think of an interface as a skeleton for the class implementing it.

say for instance IAnimal the interface will determine that the animal MUST have legs, body, face ect. so every class that implements the interface MUST have the property for each of the implemented interface properties defined inside the Interface. so if you have a class dog and you implement the IAnimal interface, dog MUST have a property for Legs AND Body AND Face.
When you INHERIT from a class ANIMAL and you specify properties in the class for Legs, Body and face. You don’t have to create the properties in the dog class because they already exist in the class inherited from.
The interface determines that it MUST have the values to be classified as an animal where Inheritance already provides properties for the animal.

When you INHERIT from a class ANIMAL you dont have to add properties in the class for Legs, Body and face because they already exist in the class inhereted from.

By: David

David — Fri, 17 Apr 2009 15:16:14 +0000

Can you please describe how using an interface would help with a circular dependancy problem in VS?

e.g.
assembly 1 references assembly 2
assembly 1 references assembly 3
assembly 3 references assembly 2

I have read that i could use an interface to remove the problem between assembly 2 and 3. This is not a design issue as both 3 and 2 are class libraries which have to be seperated.

Thanks.

By: Will Cooper

Will Cooper — Thu, 26 Mar 2009 19:13:15 +0000

This is a great article. I use interfaces but often have trouble trying to explain to others there benefit around structure and why use them at all. Many feel thye just add a layer of complexity without much benefit. If you don’t mind I’ll be using this article as it is pitched at the right level.
Many thanks

By: srivani

srivani — Wed, 04 Feb 2009 08:13:37 +0000

I havae got just abasic idea about INTERFACES
but I have not under stand what r the advantages of Interfaces for technical or flexible or developer convinense or any other

ANY WAYS THank u very much for providing this

By: piyush

piyush — Mon, 08 Dec 2008 08:19:56 +0000

i am searching for a project in vb.net and i want full information regarding about vb.net and its related topics