It's not really complicated, but it can seem so. What you need is to use the instance of the numbers class to access the list.
And that probably doesn't mean anything, but it's something you do every day and don't even think about.
So ... lets ignore it, and think about a car. Suppose you put your mobile in the glove box of your car - and then trade it in on a new one. If you open the glove box, do you expect your mobile to be there? Of course not! They are both "your car", but the actual instance of a vehicle has changed. And you know that: "your car" is different from "my car", "his car", "her car". And a single car may be accessed by several names: "your car", "this car", "that car" - the all refer to the same vehicle.
In order to drive to the shops, you need to have the right instance of a car: "your car" rather than "my car".
And classes are the same: in order to use elements of a class you need to specify which instance of the class you are talking about. Inside the class definition that's easy: you have
this (Explicitly or implicitly) which says "the current instance" whichever one it is.
But outside the class it's more complicated: you have to find the instance, and refer to it:
Car myCar = new Car("Mercedes", "A-class", Color.Black);
...
myCar.Engine.Start();</pre
<pre lang="c#">Car yourCar = new Car("Ford", "Fiesta", Color.Red);
...
yourCar.GLoveBox.Add(yourMobile);
So to access your list, you just need to supply the instance (via a variable) and specify the collection.
The other way is to make the list
static, and access it via the class name - but in that case there is only one list for all instances of the class (if you like, a static glove box would have a wormhole in it which meant the same glove box would be accessed from all cars - not practical in the real world, and probably not what you want in your app!)
Submit an article or tip