book the author discusses decoupling, but then later shows some good old T&A code (that I completely forgot about) that I know will make you scream.

You got that right! <g> I've finally resurrected my blog and have actually posted stuff in it. Even got a coupla comments already. Guess what I ranted about earlier this week? <s>

~~Bonnie



>I just went back and blew all the dust off my copy of the book - what happens is that early in the book the author discusses decoupling, but then later shows some good old T&A code (that I completely forgot about) that I know will make you scream.
>
>I think what happens (and I'm not defending it, just saying what happens) is that in many books, if the focus is on a portion of a distributed application, the authors might take shortcuts in other areas for expediency. I don't think that's always bad, especially if the author clearly explains why it's being done (the old "for purposes of this demo"), but it's the TA in particular that makes me scream.
>
>Anyway, it is still a good book that has many side benefits (it shows some good uses of ADO.NET 2.0)