How are Collection object in C# categorized?

[Karumbu]

Hello my friends , I am a student of IT , I am being practicing various program in the C# language and Java, after following your forum in the Microsoft's Visual Studio, but I was learning collection object and got stuck there , so I would like any one of you can elaborate what exactly it means and how are these collection object categorized, I am waiting for your response , would appreciate your reply.

[Steyn]

We can have a method to collect up objects as they are produced so that we can handle them as a collection and work on them together, along with referring to them independently when needed. You can use this Collection to hold up a group of objects together and then make use of it in your program the best example of the Collection object is creating an Array list that holds an array of object . I think this much is enough if you are a beginner.

[Shreevats]

There is a best example that can distinguish among the Collection objet and its properties . For example:

• A Professor object may require to step throughout all Student objects register for a specific Course that the teacher is teaching in order to calculate their grades.
• The Student Registration System (SRS) application as a in one piece might require to step throughout all of the Course objects in the present schedule of classes to conclude which of them do not yet have any students enrolled for them ,perhaps to call off these courses.

[Dwarner]

We make use of a particular type of object known as a collection to cluster other objects. A collection object can have/enclose several references to some other kind of object. Imagine of a collection like an fruitcarton, and the objects it holds like the fruits ! Both are objects, but with apparently dissimilar properties. Since collections are being used as as objects, this implies that.

• An object of the Collections should be created before they can be used . instantiated before they can first be used.
• Classes define collection that in turn describe functions for "getting" and "setting"their elements .
• The Object oriented collections are wrapped together and hence ensure data hiding.

[Jacques25]

I think I can explain you this with an example

namespace ConsoleApplication1
{
   class Program
   {
       static void Main(string[] args)
       {

           ArrayList pm = new ArrayList();
           pm.Add(5);
           pm.Add(3);
           pm.Add(7);
           pm.Add(11);
           pm.Add(13);
           pm.Add(17);
           Console.WriteLine("The Count of the Array list = " + pm.Count);
           for (int i=0; i<pm.Count; i++)
           {
               Console.WriteLine(pm[i]);
           }
           pm.RemoveAt(3);
           Console.WriteLine("The Count of the Array list = " + pm.Count);
           for (int i = 0; i < pm.Count; i++)
           {
               Console.WriteLine(pm[i]);
           }


           Console.ReadLine();
       }


       }
}

The ‘Add’ method will add a new object in the collection Array list , RemoveAt method removes the particular object at the specified index. And the count method will count the total number of objets in the array list.