.NET Tip: Creating a Collection of Your Objects Minneapolis MN

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

Genuine Genuis Solutions
(612) 872-4256
431 Clifton Ave
Minneapolis, MN
Productive Corporation
612.375.0204
510 First Ave North Suite 310
Minneapolis, MN
Global Software
(612) 305-4472
10 S 5th St
Minneapolis, MN
Dairyland Healthcare Solutions
(952) 545-6314
1550 Utica Ave S
Minneapolis, MN
Bjl Software
651-293-0102
856 Raymond Ave
St. Paul, MN
Mastermine Software
651-917-5010
840 Hampden Ave
St. Paul, MN
Assessment Systems
651-647-9220
2233 University Ave W
St. Paul, MN
Business FX Corporation
651-646-7777
2324 University Ave W
St. Paul, MN
Diversified Solutions LLC
(612) 243-1234
5932 Chicago Ave
Minneapolis, MN
Church Management Solutions
(763) 566-4212
3300 County Road 10
Minneapolis, MN

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

Genuine Genuis Solutions

(612) 872-4256
431 Clifton Ave
Minneapolis, MN