I think the problem that many authors have is "how much is too much?" they often need to abstract away a lot of the vastness that is "development" in order to focus on the subject matter the book is supposed to be delivering. I know there are the odd books that are pretty close.. But I have yet to read them myself.
To be honest, I think if you are already OK with the C# syntax, and familiar with the Framework, then you may be better focusing on books that discuss Design Patterns...
I found once I had got to grips with the C# syntax, a lot of books really started not "doing it" for me until I started reading up on design patterns. They really help you to see things as objects and creating flexible, malleable applications. The fact that it was Windows or Web was really irrelevant, and this really helped me open my mind, and got me thinking about the software as a system, not the specifics of the implementation..
This abstraction really helps in your design and allows you to focus on the individual problems - be it UI design, Data Access Layer Architecture, whatever.
Now - If I want to get better at parts of UI development, then I will get specialist books on that or DAL development, and so on..
I, and many others would strongly recommend "Head First Design Patterns" (http://www.amazon.com/Head-First-Des.../dp/0596007124
) - I think this has a bit of both, it explains each problem by describing feasable business problems and clearly demonstrates how the pattern overcomes them, and the problems/benefits each provide. Definate 5*s from me!
Hopes this gives you some food for thought, if you need anything else please give me a shout!
The Developing Developer
Currently Working Towards: MCAD C#
My Blog: http://www.robzyc.spaces.live.com
<center>"Nothing can stop the man with the right mental attitude from achieving his goal;
nothing on earth can help the man with the wrong mental attitude".