Interface Blogs

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 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. The code shown in the video can be downloaded here.