A list of all interfaces in .net 3.5SP1
in [VB.NET]
|
From: Andy B. on 23 Feb 2010 13:50 I want to make some wise choices when making my objects. I want to add features to them, but don't feel like writing my own interfaces if they already exist. Since I don't totally know what's out there in .net 3.5sp1 as far as interfaces go, is there a simple easy way to find a list of them somewhere? I would need them from msdn if possible.
From: Family Tree Mike on 23 Feb 2010 18:27 On 2/23/2010 1:50 PM, Andy B. wrote: > I want to make some wise choices when making my objects. I want to add > features to them, but don't feel like writing my own interfaces if they > already exist. Since I don't totally know what's out there in .net 3.5sp1 as > far as interfaces go, is there a simple easy way to find a list of them > somewhere? I would need them from msdn if possible. > > The only place I would trust would be MSDN. All the namespaces list on their main page, the classes, structures, and interfaces that are defined in the namespace. You need to identify what namespace might have appropriate interfaces for your objects. For example, if your class does something with multiple objects, you would likely look at System.Collections: http://msdn.microsoft.com/en-us/library/system.collections.aspx -- Mike
From: Andy B. on 23 Feb 2010 18:39 "Family Tree Mike" <FamilyTreeMike(a)ThisOldHouse.com> wrote in message news:OApHD$NtKHA.5940(a)TK2MSFTNGP02.phx.gbl... > On 2/23/2010 1:50 PM, Andy B. wrote: >> I want to make some wise choices when making my objects. I want to add >> features to them, but don't feel like writing my own interfaces if they >> already exist. Since I don't totally know what's out there in .net 3.5sp1 >> as >> far as interfaces go, is there a simple easy way to find a list of them >> somewhere? I would need them from msdn if possible. >> >> > > The only place I would trust would be MSDN. All the namespaces list on > their main page, the classes, structures, and interfaces that are defined > in the namespace. You need to identify what namespace might have > appropriate interfaces for your objects. For example, if your class does > something with multiple objects, you would likely look at > System.Collections: > http://msdn.microsoft.com/en-us/library/system.collections.aspx > > > -- > Mike Got that part, but is there a way to list only the interfaces?
From: Cor Ligthert[MVP] on 24 Feb 2010 00:19 Andy, I can not imagine a situation where you would use an existing interface (from Net) except for non inheritable classes. If you want to create classes from already existing classes then you use those classes as a base class. Those then already implement those interfaces. It seems that somehow interfaces have blinded you. Cor "Andy B." <a_borka(a)sbcglobal.net> wrote in message news:er6BbkLtKHA.1608(a)TK2MSFTNGP05.phx.gbl... > I want to make some wise choices when making my objects. I want to add > features to them, but don't feel like writing my own interfaces if they > already exist. Since I don't totally know what's out there in .net 3.5sp1 > as far as interfaces go, is there a simple easy way to find a list of them > somewhere? I would need them from msdn if possible. >
From: Family Tree Mike on 24 Feb 2010 07:57
On 2/24/2010 12:19 AM, Cor Ligthert[MVP] wrote: > Andy, > > I can not imagine a situation where you would use an existing interface > (from Net) except for non inheritable classes. > > If you want to create classes from already existing classes then you use > those classes as a base class. > Those then already implement those interfaces. > > It seems that somehow interfaces have blinded you. > > Cor > > > > "Andy B." <a_borka(a)sbcglobal.net> wrote in message > news:er6BbkLtKHA.1608(a)TK2MSFTNGP05.phx.gbl... >> I want to make some wise choices when making my objects. I want to add >> features to them, but don't feel like writing my own interfaces if >> they already exist. Since I don't totally know what's out there in >> .net 3.5sp1 as far as interfaces go, is there a simple easy way to >> find a list of them somewhere? I would need them from msdn if possible. >> System.IComparable might be an exception to this. There is often good reason to impliment this interface. -- Mike |