I strongly believe in learning the basics. I'll start by writing console applications - take the collections, IO, the language itself (be it VB or C #, or even something else).
It's probably worth learning a bit of βnormalβ WPF after that, on the grounds that it might be easier to experiment this way than with Silverlight. (I cannot say that I have already written any Silverlight.)
If you dive right into Silverlight when you encounter problems, you will not recognize, because you are not familiar with the language, the underlying platform, or Silverlight itself. In your opinion, you will take a little more time to go to my offer above, but as soon as you leave, it will be a much smoother trip, in my opinion.
source share