What pattern is layered architecture in asp.net?

I am a asp.net developer and don't know much about patterns and architecture. I will very thankful if you can please guide me here.

In my web applications I use 4 layers.

1. Web site project (having web forms + code behind cs files, user controls + code behind cs files, master pages + code behind cs files)

2. CustomTypesLayer a class开发者_如何学Python library (having custom types, enumerations, DTOs, constructors, get, set and validations)

3. BusinessLogicLayer a class library (having all business logic, rules and all calls to DAL functions)

4. DataAccessLayer a class library( having just classes communicating to database.)

-My user interface just calls BusinessLogicLayer. BusinessLogicLayer do proecessign in it self and for data it calls DataAccessLayer functions.

-Web forms do not calls directly DAL.

-CustomTypesLayer is shared by all layers.

Please guide me is this approach a pattern ? I though it may be MVC or MVP but pages have there code behind files as well which are confusing me.

If it is no pattern is it near to some pattern ?

That's not four layers, that's three layers, so it's a regular three tier architecture.

The CustomTypesLayer is not a layer at all. If it was, the user interface would only use the custom types layer and never talk to the business layer directly, and the data access layer would never use the custom types layer.

The three tier architecture is a Multitier architecture

As far as patterns go, I recommend getting to grips with these:

• My biggets favourite by a mile is the Dependency Inversion Principle (DIP), also commonly known as (or at least very similar to) Inversion of control (IoC) ans Dependencey Injection; they are quite popular so you should have no problem finding out more info - getting examples. It's really good for abstracting out data access implementations behind interfaces.
• Lazy Load is also useful. Interestingly, sometimes you actually might want to do the opposite - get all the data you need in one big bang.
• Factory pattern is a very well known one - for good reason.
• Facade pattern has also helped me keep out of trouble.

Wikipedia has a pretty good list of Software design patterns, assuming you haven't seen it yet.

A final thing to keep in mind is that there are three basic types of patterns (plus a fourth category for multi-threaded / concurrency); it can help just to know about these categories and to bear them in mind when you're doing something of that nature, they are:

• Creational
• Structural
• Behavioral

Take a look at the Entity Framework or LinqToSQL. They can both generate your data access layer automatically from your database. This will save you a lot of (boring) work and allow you to concentrate on the interesting layers.

Code-behind does not really have anything to do with architecture - it is more of a coding style. It is a way of separating logic from presentation. Any architecture you mention can be used with or without code-behind.

You seem to be describing a standard three-tier architecture. MVC is a pattern than describes how your layers and the user interact. The user requests a page (represented by a View), which requests its data from the Controller. The Controller communicates with your business layer (Model) to extract the correct data and passes it to your View for display. If the View is interactive, for instance it allows the user to update something, then this user action action is passed back to your Controller, which would call the relevant method against the business layer to save the update to the database.

Hope this helps.