Object Oriented Data Access in ASP.NET 2.0 – Part 1
by Kevin Koch

With the complexity of applications these days, developers must take special care to make sure that their code is robust, scalable and re-usable. Depending on the size of the application you’re creating the thought of manually coding your own data access layer might seem like a huge overhead.

The problem with some of the controls provided by the .NET framework is that they essentially eliminate the developer from the coding equation, and instead provide default built in plumbing for a lot of common features an application may require. If your client requires a very simple, small scale application that only provides a minimal set of features you can usually get away with this approach.

- OR -

Kevin Koch

Kevin KochKevin Koch is a senior software engineer with over 8 years experience designing and architecting primarily web based applications. Fresh out of college during the nineties he co-founded Task Solutions and developed several projects with the then popular classic ASP.

During the Dot Com boom Kevin left his position as president and joined a new venture to build an enterprise insurance claim system build upon J2EE technology. After the Dot Com crash Kevin schooled himself to become an expert with .NET technology and is currently freelancing his ASP.NET skills to build enterprise n-tier frameworks using advanced OO methodologies.

See All Postings From Kevin Koch >>

Place your review about Object Oriented Data Access in ASP.NET 2.0 – Part 1

You must me logged in to write a review

Be the first to place a review