.NET Tip: Creating a Collection of Your Objects Buffalo NY

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

CTG - Corporate Headquarters
(716) 882-8000
800 Delaware Ave.
Buffalo, NY
Network Critical NA, LLC
(716) 558-7280
3675 Harlem Rd.
Buffalo, NY
Samuels Consulting
(858) 531-6000
42 Willowlawn St.
Buffalo, NY
Kingman Bassett, Consultants
(716) 856-3418
188 Soldiers Pl.
Buffalo, NY
Utilant, LLC
(888) 884-5268
475 Ellicott St., Apt. 5
Buffalo, NY
COMAND Solutions
(800) 598-0869 ext. 88
110 Elmwood Ave.
Buffalo, NY
M Power Specialists, LLC
(716) 842-8787
232 Delaware Ave., Ste. 20
Buffalo, NY
DBNET Innovative Technology, LLC
(716) 604-0684
34 Schutrum St.
Buffalo, NY
devExperts
(716) 510-8262
222 Wallace Ave.
Buffalo, NY
MVP Network Consulting, LLC
(716) 630-1701 ext. 202
1297 Hertel Ave.
Buffalo, NY

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

CTG - Corporate Headquarters

(716) 882-8000
800 Delaware Ave.
Buffalo, NY