Comments on: Introduction to Interfaces in VB.NET http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/ Articles on VB.NET and Software Development Team Leadership Wed, 08 Feb 2012 00:39:42 +0000 http://wordpress.org/?v=2.7.1 hourly 1 By: Tjaart http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/comment-page-1/#comment-1457 Tjaart Thu, 04 Mar 2010 09:44:54 +0000 http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/#comment-1457 For people who dont understand interfaces: Interfaces make your code pluggable because you know when something implements a certain interface that it has certain functions or properties. IEnumerable for example lets you know that you have an enumarable indexable list of items. Say you want to write a function that can take arrays or lists. Both implement IEnumerable, so instead of writing an overloaded function to cater for both types, you simply make your function parameter an IEnumerable. Example: Private Function RandomizeItems(ByVal items as IEnumerable) instead of Private Function RandomizeItems(ByVal items as List(Of T)) Private Function RandomizeItems(ByVal items as T()) Get it? For people who dont understand interfaces:

Interfaces make your code pluggable because you know when something implements a certain interface that it has certain functions or properties.

IEnumerable for example lets you know that you have an enumarable indexable list of items. Say you want to write a function that can take arrays or lists. Both implement IEnumerable, so instead of writing an overloaded function to cater for both types, you simply make your function parameter an IEnumerable. Example:

Private Function RandomizeItems(ByVal items as IEnumerable)

instead of

Private Function RandomizeItems(ByVal items as List(Of T))

Private Function RandomizeItems(ByVal items as T())

Get it?

]]> By: Adel http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/comment-page-1/#comment-1454 Adel Tue, 23 Feb 2010 00:00:09 +0000 http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/#comment-1454 My understanding is that in .NET technology ,you can not inherit multiple classes .However, it is possible in VC++ e.g. in .NET a class has one and only one parent(derived Class) furthermore, it could implement more than one interface except that it takes only the declaration parts not the implementation. In fact, it is meaningless if some class has more than one father it only inherits its father's wealth(Properties and methods) and spends (implements) it. On other hand,it can not inherits other parties' wealth but it may spend (implement) it. My understanding is that in .NET technology ,you can not inherit multiple classes .However, it is possible in VC++
e.g. in .NET a class has one and only one parent(derived Class)
furthermore, it could implement more than one interface except that it takes only the declaration parts not the implementation.
In fact, it is meaningless if some class has more than one father
it only inherits its father’s wealth(Properties and methods) and spends (implements) it.
On other hand,it can not inherits other parties’ wealth but it may
spend (implement) it.

]]> By: Alexandre http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/comment-page-1/#comment-1452 Alexandre Tue, 16 Feb 2010 12:52:37 +0000 http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/#comment-1452 I am very gladed to see such code of interface in vb dot net I am very gladed to see such code of interface in vb dot net

]]> By: Timan http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/comment-page-1/#comment-1432 Timan Tue, 01 Dec 2009 18:54:57 +0000 http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/#comment-1432 What is the real time use of Interface??? What is the real time use of Interface???

]]> By: pratap http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/comment-page-1/#comment-1428 pratap Wed, 11 Nov 2009 11:14:21 +0000 http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/#comment-1428 what is the benefits of using interface? what is the benefits of using interface?

]]> By: Suresh http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/comment-page-1/#comment-1427 Suresh Sat, 31 Oct 2009 18:22:36 +0000 http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/#comment-1427 Very Nice Article on Interfaces! Can you provide me an real time example of when and where to use interfaces. Very Nice Article on Interfaces!

Can you provide me an real time example of when and where to use interfaces.

]]> By: Lakshmi http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/comment-page-1/#comment-1423 Lakshmi Tue, 27 Oct 2009 05:04:33 +0000 http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/#comment-1423 can u explain why we need to go for interfaces rather than calling a method.. Let me know whats the difference... can u explain why we need to go for interfaces rather than calling a method.. Let me know whats the difference…

]]> By: AnonNoob http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/comment-page-1/#comment-1392 AnonNoob Mon, 07 Sep 2009 17:34:50 +0000 http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/#comment-1392 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. 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 http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/comment-page-1/#comment-1364 Mohsin Mon, 15 Jun 2009 10:26:36 +0000 http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/#comment-1364 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. 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 http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/comment-page-1/#comment-1359 mukund Tue, 02 Jun 2009 08:31:24 +0000 http://vbnotebookfor.net/2007/10/23/introduction-to-interfaces-in-vbnet/#comment-1359 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 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

]]>