Thanks for the incredibly kind words, but nope, not writing a book on WPF. Did release a book called Programming .NET 3.5 which does something very different TOC here[^]. For me, the best WPF book has to be Sells and Griffiths -- that is truly one of the best language/frameworks books I've read. Programming C# was my pride and joy but I let myself down with the latest edition; live and learn. I'm convinced Programming Silverlight[^]will be incredible if I ever finish it (which is what I should be doing, rather than writing this!) The key thing, I think, is that while there are some books that are clearly bad, what makes a book good for one person may be precisely what makes it bad for another. The attributes I hear about most are relative terseness, assumptions about what the reader already knows, how well each chapter stands on its own, number and complexity of examples given, and that most subjective attribute: style. I often tell the story of my second year writing (1897 I think it was) when I received two letters. The first said (more or less) "You saved my life. Never before could anyone explain pointers in a way I could understand..." The second one said (verbatim!) "I don't know what it is you do for a living, but it sure as hell isn't programming or writing, because you are incompetent at both." I had them up on my wall for years. -jesse Jesse Liberty