.NET Tip: Creating a Collection of Your Objects Greensboro NC

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

L A Solutions
336-389-1707
110 E Washington St
Greensboro, NC
Software Design Inc
336-378-0900
1301 Carolina St
Greensboro, NC
Data Management Corp
336-275-1697
423 Eugene CT
Greensboro, NC
Compucon USA LLC
336-294-0604
620 Green Valley Rd
Greensboro, NC
COMPUTER TROUBLESHOOTING
336-510-7919
1400 Battleground Ave
Greensboro, NC
Spi Software Solutions
336-333-2967
2007 Yanceyville St
Greensboro, NC
Advantec Information Systems LLC
336-275-2832
2007 Yanceyville St
Greensboro, NC
D P Solutions Inc
336-854-7700
4411 W Market St
Greensboro, NC
Dalcom Consulting
336-851-1802
8 Oak Branch DR
Greensboro, NC
Engineered Software
336-299-4843
615 Guilford College RD
Greensboro, NC

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

L A Solutions

336-389-1707
110 E Washington St
Greensboro, NC
http://www.lasolutions.net