Just reading a book on programming makes no sense, because Without a set of code information is not much. I would recommend doing so:
invent a task that you want to solve (for example, a catalog of books for storage on your PC);
choose a technology (WinForms, WPF, ASP.NET, Silverlight), if you just read the book, then it’s better to start with Forms, because other technologies will require knowledge of markup (XAML, HTML, etc.), a very good understanding of OOP (WPF has everything on the patterns :));
and write code ... in the process you step on a bunch of rakes, get into books, into the network ... start thinking about architecture.
In general, if you understand the OOP, I recommend reading Object-Oriented Design Techniques. Design patterns . It is difficult to read, but if you understand - look at the program in another way :).
By C # Richter recommend. (He started with Troelsen himself)