.NET Tip: Creating a Collection of Your Objects Saint Louis MO

The generic collection introduced with .NET 2.0 allows you to create collections of your objects without having to design a new class.

Local Companies

Open Software Technology
314-854-9138
7777 Bonhomme Ave
St. Louis, MO
Engineering Software International
314-352-4700
4545 Oleatha Ave
St. Louis, MO
New Horizons Software Inc
314-961-4335
801 Leonard DR
St. Louis, MO
E Data Solutions Inc
314-446-1555
315 Lemay Ferry RD
St. Louis, MO
Bemas Software Inc
314-439-5300
7 The Pines CT
St. Louis, MO
Digital Consulting & Software
314-682-2350
12655 Olive Blvd
St. Louis, MO
Foundry Software Development Co
314-993-3732
721 Emerson RD
St. Louis, MO
Wonderware Central
888-676-9933
Two City Place Drive
St. Louis, MO
STL EHR Group
314-477-7459
689 Craig Road
Creve Coeur, MO
Client Server Solutions Inc
314-523-4400
2008 Altom CT
St. Louis, MO

provided by: 
Originally published at Internet.com


One of the new language features introduced with .NET 2.0 was the generic collection. In the past, even as far back as Visual Basic 6.0, you could create a custom collection class for your classes. With .NET 1.0/1.1, you could add objects to standard collection classes like the ArrayList and the Hashtable classes. However, when you looked at the members of those collections, they were not strongly typed and had to be cast back to the original type.

The generic collection allows you to create collections of your objects without having to design a new class. Take, for example, the ValidationError class I created for a previous tip: public class ValidationError { private string _error; public string ErrorMessage { get { return _error; } set { _error = value; } } public ValidationError(string errorMessage) { ErrorMessage = errorMessage; } }

If you wanted to create a collection of ValidationError objects, you could put them in an ArrayList. However, using a generic collection as shown in the following snippet requires a bit less overhead: List errors = new List(); errors.Add(new ValidationError("Error #1")); errors.Add(new ValidationError("Error #2")); errors.Add(new ValidationError("Error #3")); errors.Add(new ValidationError("Error #4")); foreach (ValidationError err in errors) { Response.Write(err.ErrorMessage + "
"); }

By using the generic List declaration, you create a collection of your custom objects without any extra work. As the snippet shows, you now can loop through the collection and .NET avoids all the extra overhead of converting a generic member of an ArrayList to a ValidationError object.

Several other generic collections are available for other situations. Refer to the help file for more information on this handy new feature.

About the Author

Eric Smith is the owner of Northstar Computer Systems, a web-hosting company based in Indianapolis, Indiana. He is also a MCT and MCSD who has been developing with .NET since 2001. In addition, he has written or contributed to 12 books covering .NET, ASP, and Visual Basic. Send him your questions and feedback via e-mail at questions@techniquescentral.com.

Author: Eric Smith

Read article at Internet.com site

Featured Local Company

Open Software Technology

314-854-9138
7777 Bonhomme Ave
St. Louis, MO