Contents tagged with ADO.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.
In this video tutorial I walk through the fundamentals of creating an N-Layer ASP.NET application. What's "N-Layer" you ask? N-Layer can be interpreted many different ways, but I generally use the term to mean separating presentation, business and data code into individual code layers. Doing this allows code to be re-used throughout an application and prevents unnecessary clutter in ASP.NET code-behind classes. This video covers creating presentation, business and data layers and also covers another layer I normally add to projects that I refer to as "Model". The model layer contains data entity classes that are used to pass data between the different layers.
If you're currently embedding all of your code directly in ASP.NET pages, this video will help get you started on the road to recovery. I'm kidding of course, but if you want to build more re-useable and maintainable applications you'll want to segregate your code into different layers at a minimum. Other types of architectures can certainly be applied as well.
One of the talks I gave at the 2006 ASP.NET Connections conference in Las Vegas covered using TableAdapters and strongly-typed DataSets. TableAdapters offer a great way to create a data-tier that work with stored procedures or inline SQL without writing much (if any) code. They can be used to insert, update or delete data as well as select data into strongly-typed DataSets.