Finding type of objects in a collection

[John Spiegel]

Hi all,

I'm trying to create a subclass of an ArrayList that is intended
specifically for holding FileInfo objects. My idea to restrict this is to
override the Add and AddRange methods to allow only FileInfo objects. In
AddRange, how can I verify that the collection passed is a collection of
FileInfo objects?

TIA,

John

[Joshua Flanagan]

It is generally recommended to derive from CollectionBase instead of
ArrayList for your custom collections. Check out this article for some
hints:
http://www.c-sharpcorner.com/Code/20...ollections.asp

You can then create your own AddRange method that only accepts a
FileInfo array:

public void AddRange(FileIn fo[] files)

If you want to stick with overriding the ArrayList, I don't think there
is anything you can do aside from looping over the collection and
checking the type of each object in the collection. It probably won't
be the most performant code, and you probalby lose the performance
benefit of the AddRange method.

public override void AddRange(System .Collections.IC ollection c) {
foreach(object item in c){
if (!item is System.IO.FileI nfo) {
throw new ArgumentExcepti on("");
}
base.AddRange(c );
}

Instead of throwing an exception if one item is bad, you could just
ignore the objects that are not FileInfos, and call base.Add(item) for
the ones that are.

Joshua Flanagan
http://flimflan.com/blog
John Spiegel wrote:

Hi all,

I'm trying to create a subclass of an ArrayList that is intended
specifically for holding FileInfo objects. My idea to restrict this is to
override the Add and AddRange methods to allow only FileInfo objects. In
AddRange, how can I verify that the collection passed is a collection of
FileInfo objects?

TIA,

John

[John Spiegel]

Thanks, Joshua. Will look at that CollectionBase idea!

- John
"Joshua Flanagan" <jo**@msnews.co m> wrote in message
news:u7******** ******@TK2MSFTN GP09.phx.gbl...

It is generally recommended to derive from CollectionBase instead of
ArrayList for your custom collections. Check out this article for some
hints:
http://www.c-sharpcorner.com/Code/20...ollections.asp

You can then create your own AddRange method that only accepts a FileInfo
array:

public void AddRange(FileIn fo[] files)

If you want to stick with overriding the ArrayList, I don't think there is
anything you can do aside from looping over the collection and checking
the type of each object in the collection. It probably won't be the most
performant code, and you probalby lose the performance benefit of the
AddRange method.

public override void AddRange(System .Collections.IC ollection c) {
foreach(object item in c){
if (!item is System.IO.FileI nfo) {
throw new ArgumentExcepti on("");
}
base.AddRange(c );
}

Instead of throwing an exception if one item is bad, you could just ignore
the objects that are not FileInfos, and call base.Add(item) for the ones
that are.

Joshua Flanagan
http://flimflan.com/blog
John Spiegel wrote:

Hi all,

I'm trying to create a subclass of an ArrayList that is intended
specifically for holding FileInfo objects. My idea to restrict this is
to override the Add and AddRange methods to allow only FileInfo objects.
In AddRange, how can I verify that the collection passed is a collection
of FileInfo objects?

TIA,

John