William
Sun Dec 21 15:25:52 CST 2003
You are right....I read it a while ago, but I'll second the motion that it's
a great book. A lot different from a lot of other approaches, but very cool
nonetheless.
"William (Bill) Vaughn" <billvaRemoveThis@nwlink.com> wrote in message
news:OMwfERzxDHA.1856@TK2MSFTNGP09.phx.gbl...
> I also like Rocky Lhotka's book
>
http://www.amazon.com/exec/obidos/ASIN/1590591453/qid=1071950541/sr=2-1/ref=sr_2_1/103-3385934-7563819
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> MVP, hRD
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> __________________________________
>
> "William Ryan" <dotnetguru@nospam.comcast.net> wrote in message
> news:u9kcJwwxDHA.2408@tk2msftngp13.phx.gbl...
> > There are a few good books out there, but I'd start here..
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/daab-rm.asp
> >
> > Here's a pretty good book on the subject..
> >
>
http://www.amazon.com/exec/obidos/tg/detail/-/0672322331/qid=1071933120//ref=sr_8_xs_ap_i4_xgl14/103-9800292-3237457?v=glance&s=books&n=507846
> >
> > And this one too...
> >
>
http://www.amazon.com/exec/obidos/tg/detail/-/0735618399/qid=1071933185/sr=1-1/ref=sr_1_1/103-9800292-3237457?v=glance&s=books
> >
> > Also Daniel, getting a firm grip of how ADO.NET works is the key to
> building
> > anything based upon it, Enterprise or Standalone. You will probably
want
> to
> > get Bill Vaughn's Best Practices book... www.betav.com or David
Sceppa's
> > ADO.NET COre Reference, they will pay for themselves by the time you get
> to
> > the office...
> >
> > HTH,
> >
> > Bill
> > "ViperDK (Daniel K.)" <viper_usenet_acc@viperdk.dyndns.org> wrote in
> message
> > news:bs1k68$rsg$06$1@news.t-online.com...
> > > Could someone give me a hint where to find *good* information,
samples,
> > > tutorials, hints, whatever on design of multi/three-tiered
applications,
> > > business layers etc (mainly winforms but web application information
> isn't
> > > bad, too)? ok, that isn't especially on enterprise size application
but
> on
> > > applications that are well designed, changeable and maintainable.
> > >
> > > the things that interest me are especially
> > > - database abstraction, where it makes (not) sense, to use advanced db
> > > functions or use it only as backend, and why in which case
> > > - how and which layers/baseclasses to use in the code, best with code
> > > samples through the layers
> > > - how and at which level to let the different (data)objects interact
> with
> > > others
> > > - how to make sql queries. directly as strings or via classes that
could
> > > make porting to other databases more easyly
> > >
> > > guess this are things that the most companys make themselves without
> > knowing
> > > the drawbacks of their sw-designs.i'd like to know how to make it real
> > good
> > > and not to write some code without any good concept and in the hope
that
> > it
> > > "seems to work" somehow in the end :)
> > >
> > >
> > > thx in advance,
> > > Daniel
> > >
> > >
> >
> >
>
>