Quote Originally Posted by techgnome View Post
True... but I think with programming concepts, it becomes a bit more so.... I mean, if I'm searching for a recipie for something, I can usually narrow it down some, even if I don't know quite what I'm looking for. But for programming terms... it becomes a bit more esoteric. Somethings are obvious... like searching for DataSets or DataTables.... things like Generic classes..... not so much.

-tg
This is quite true, which is why noone should try to learn anything directly from a reference only. For example, as has been said, a dictionary is no use to you if you don't know how to spell a word but dictionaries are not intended to teach you how to spell. They are intended to provide you a pronunciation and definition of words that you already know how to spell. MSDN is a reference, not a tutorial. There are plenty of beginner tutorials on the web and in books that will teach you the basics. Once you have those basics, then you DO know what to look for on MSDN.

Having said that, this thread emerged simply because the OP doesn't understand how reference type objects work. If they had then they'd have known that assigning the value of one variable to another does not create a copy of the referenced object. It's not for the List(Of T) documentation to explain that. That's the sort of thing that most web- or book-based tutorials teach early on because it's so fundamental to .NET programming. Reference documentation doesn't teach you programming fundamentals. The day it does is the day it stops being good reference documentation.