>>A book isn't going to do it. If you want to learn C#, you need a real project and force yourself to use it.
>
>True, that about force. I remember there were some languages where I had to force myself - let's see, the PDP-11 command language (sort of interesting, but hated it), Hayes codes for modems, ESC/P, the HP printer language, GwBasic (which was just plain fugly compared to GfA or even Spectrum or Spectrum Beta dialects), OPL for Psion and a few oddballs more. Even Cobol didn't require force - it was curiosity that led me into learning. I guess trying to learn Cobol now would require forcing myself, just like C# would. They're both too verbose - in Cobol you had to do all the work for the compiler (define all the variables and buffers, what with data types and lengths); in dot net you need to know the hierarchy of anything you want to use, and there's too much of it. Intellisense will get you the next name in the sausage, but you still need to know where the sausage needs to start. And you may be using a piece of abandonware at that.

When I think back on all the languages I've learned and used - there has never been force involved. I wanted to learn and played with them to do interesting things. First thing I did in c# was not a hello world - which is utterly useless - but a little loop to scale an image down and back up. Frankly it is all sausage! :)