Hi,
The statement:
"Dim words() As String = text.Split(" ".ToCharArray())"
on page 279 of the book "Beginning VB.NET", is very difficult to understand if one not simply taking the simple explanation on pg. 281. I tried to browse through the MSDN, but I am getting nowhere because the MSDN is too "technically" written.
In such a huge libary of objects in VB.NET, I wonder is there any "magic" way for one to get a better grip on what properties & functions to use and set them right for a given task, and how to comprehend the MSDN document.

Many thanks!

John Lam

Yo! I guess the reason you are getting no answers to this very sensible question is because there is no easy answer. People like to say that with repeated practice, and persistent working through details like the one you mention, using excellent books like ours, you will steadily absorb enough background and mindset to be able to struggle through the MSDN documentation. I am not there by a long shot, and I often despair as to the great gulf I must bridge, and I forget too readily what I learned last month. Certainly there is an aptitude situation. Many of us just do not have the required smarts to be capable of getting there. When should I give up? There is good help here on some topics, but have received no answer on my own question on printing and Crystal Reports.
Yassou!

Hi guys.

I have been away and this post reminded me that there were some outstanding questions. I will post some answers right away ;)

With regards to MSDN.
I think that everyone struggles with the MSDN docs nd books.
There are many combinations of functions and interfaces, when to use, when not to use etc. There probably won't ever be a "special guide".
Generally, most do say - it is when you gain experience. But I know great smart people who still struggle. I too sometimes look at an MSDN section and simply have to throw my hands in the air.

With MSDN you tend to need the correct words, terms or phraze to get a decent result which may or may not be helpful.

There are definite learning curves too, but I wouldn't ever say you do not have the smarts for it. if you got this far, you have got the smarts.

with regards to learning curves.
I have counted about 15 large curves for me so far in my life as a developer. Just when you think you are there, there is another hill behind another door. It slowly gets easier. personally I think that all go through with varying degrees.

My advice, keep it up and keep writing code.
its like air miles, each 10 000 lines of code helps you climb the hill.
:)

btw: a very nice place to search for stuff is http://groups.google.com

if you search for "vb.net split" you will find quite a bit of info that may help you.

Jonathan Crossland
http://www.jonathancrossland.com

Thanks Jon. I'll keep plugging away grimly. Yassou!