Using ADO.NET in an N-Layer Application Architecture

Thursday, September 20, 2007

.NET ADO.NET ASP.NET

I'm teaching a C# programming course this week at Interface Technical Training and promised that I'd post some demo code that demonstrates how to segregate code into multiple layers (presentation, business, and data) while using ADO.NET. The code can be downloaded here.

Awhile back I put together a video that walks through the fundamentals of creating N-Layer/N-Tier applications. The video can be viewed here.

Follow me on Twitter @DanWahlin

Subscribe to my Free FlipBoard Magazines:

3 Comments (previous comments before moving to Disqus)

I think you should drop ADO.Net 100% and move to LINQ. I suggest the same thing to everyone.

Timothy Khouri - Friday, September 21, 2007 1:31:21 AM

Great idea....except LINQ isn't even out yet and won't be available for use in many corporations until .NET 3.5 has been out awhile and "proven". So, although I agree with you that LINQ should be used since it has some very cool capabilities, that's not reality for many developers at this stage of the game.

dwahlin - Friday, September 21, 2007 6:07:59 AM

Thanks for the class last week, it clarified much...

Harry - Wednesday, September 26, 2007 2:07:04 PM

Subscribe to my Free FlipBoard Magazines:

3 Comments (previous comments before moving to Disqus)