Data layers in n-tier ASP.NET 2.0 applications

  • Thread starter Thread starter mark.norgate
  • Start date Start date
M

mark.norgate

Hello

I'm looking for resources and advice on how best to implement a
scalable data layer in an n-tier ASP.NET 2.0 application.

I understand the ADO.NET classes, and I'm a reasonably competent
programmer but I've never really tried to implement an enterprise scale
application in .NET before, so don't know how best to go about it. I'm
not really interested in books with titles along the lines of
"Beginners guide to blah" since I'm not really a beginner and have
consumed most of the MSDN documentation in my search for answers.

I've looked at various internet resources, such as those on
www.codeproject.com and so on, but they're not entirely satisfactory
unfortunately. I did a book search on Amazon for "ASP.NET 2.0 data" and
got a whole list of books relating to death, strangely. I've seen
various books that suggest writing an object-oriented interface to my
database, and although that seems like an excellent idea, it doesn't
really help me in terms of separating the various layers of the
application onto potentially different machines.

Maybe I'm revealing my ignorance, so any pointers to books/internet
resources/etc would be greatly appreciated.

Mark
 
My God.

Scrap that post. Have just discovered a huge node in the MSDN Library
that I'd previously missed devoted to application architecture. Not
sure that it will actually cover the nuts and bolts of data layer
implementation though.

I have some reading to do...

Mark
 
Back
Top