Walkthrough: Creating the Data Access and Business Logic Layers in ASP.NET
When you work with data in ASP.NET, you will benefit by using common software patterns. One of these patterns is to separate the data-access code from the business-logic code that governs access to the data or that provides other business rules. In this pattern, these two layers are separate from the presentation layer, which consists of the pages that the Web site user accesses to view or change data.
A Visual Studio Web site project with source code is available to accompany this topic: Download.
ASP.NET can provide separation between data access, business logic, and presentation in several ways. For example, the data source model, which includes server controls such as the LinqDataSource and ObjectDataSource controls, separates the presentation layer from the data-access code and the business logic.
Another pattern is to include the data-access logic directly in the ASP.NET pages (the presentation layer). For example, you might write ADO.NET code in the ASP.NET page's code-behind page or use the SqlDataSource control. This approach tightly couples the data-access logic with the presentation layer.
The recommended approach is to separate the data access logic from the presentation layer. This separate layer is referred to as the data-access layer. The data-access layer can be implemented as a separate Class Library project. However, you can also use tools in Visual Web Developer that can generate a data-access layer for you.
You cannot create a class library project in Microsoft Visual Web Developer Express. However, you can create a separate project by using Visual Basic Express or Visual C# Express and then include the output from that class as an assembly (DLL) in the Web site.
If your Web site displays or updates data, you should create a data-access layer and business-logic layer before creating the user interface.
A data-driven Web application usually includes a data-access layer by using typed datasets or entity classes that represent the data. It also includes a business-logic layer that enforces custom business rules. Finally, it includes a presentation layer by using ASP.NET pages, and by using master pages and themes to create a common page layout. This walkthrough shows how to create a data-access layer.
The data-access layer includes all the code that is specific to the underlying data source. This includes code that creates a connection to the database and that issues Select, Insert, Update, and Delete commands. The data-access layer typically contains classes that implement methods for accessing the underlying database data. The presentation layer does not directly work with data. Instead, it invokes classes and methods in the data-access layer for all data requests. You can customize these classes using your own business logic.
Tasks illustrated in this walkthrough include the following:
Creating a SQL database and adding data.
Adding a LINQ to SQL file that acts as the data-access layer.
Creating a page that works as the presentation layer.
Adding a LinqDataSource control to a page that communicates between the presentation layer and the data-access layer.
To complete the walkthrough, you will need the following:
Visual Studio or Visual Web Developer Express installed on your computer.
If you are using Visual Studio, the walkthrough assumes that you selected the Web Development collection of settings when you started Visual Studio the first time. For more information, see How to: Select Web Development Environment Settings.
SQL Server Express. If you have Microsoft SQL Server installed, you can use that instead.
Creating A Web Site
The first step is to create a Web site.
This walkthrough uses a Web site project. You could use a Web application project instead. For information about the difference between these Web project types, see Web Application Projects versus Web Site Projects.
To create a new file system Web site
Open Visual Studio or Visual Web Developer Express.
In the File menu, click New Web Site.
The New Web Site dialog box is displayed.
Under Installed Templates, click Visual Basic or Visual C# and then select ASP.NET Web Site.
In the Web location box, select File System, and then enter the name of the folder where you want to keep the pages for your Web site.
For example, type the folder name C:\WebSites.
Visual Studio creates a Web site project that includes prebuilt functionality for layout (a master page, the Default.aspx and About.aspx content pages, and a cascading style sheet), for Ajax (client script files), and for authentication (ASP.NET membership).
Connecting to a Database
The next step is to connect to a database in Visual Web Developer by using the Server Explorer window. (In Visual Web Developer Express, the window is named Database Explorer.) Creating a connection to a database in Server Explorer lets you add tables, stored procedures, views, and other database elements, all within Visual Studio. You can also view table data or create queries manually or by using the Query Builder window.
When you build the typed dataset for the data-access layer later in this walkthrough, you must create a connection in Visual Web Developer to the database. You can provide the connection information manually. However, Visual Web Developer can simplify this process because it automatically populates a list of the databases that are already registered in Server Explorer.
For this walkthrough you will create a new database for tracking task items.
Creating a New SQL Server Express Database
In this section you will create a new SQL Server Express database that will store task information for a to-do list.
To add a database to the Web site
In Solution Explorer, right-click the name of the Web site and then click Add New Item.
The Add New Item window is displayed.
Select SQL Database and name the database Tasks.mdf.
When Visual Web Developer asks you whether the database should be stored in the App_Data folder, click Yes.
Creating a Schema and Sample Data for the Tasks Database
You can use the database design and editing features to create a schema for the table that stores the task items.
To define a schema and add data for the Tasks database
In Solution Explorer, open the App_Data folder and double-click Tasks.mdf.
The Tasks database node is opened in Server Explorer.
Right-click the Tables folder and then click Add New Table.
The table definition window is displayed.
Create the following columns in the table:
Select the row for the taskId column, right-click the row, and then click Set Primary Key.
In the Properties window, set the Identity Column property to the taskId column.
Save the table, name it TasksList, and then close the table-definition window.
Right click the table in Server Explorer and then click Show Table Data.
An editing window is displayed where you can view, add, and edit the data.
Add four or five records to the table.
You do not have to specify a value for the taskId column, because it is an identity column and its value is automatically assigned.
Close the editing window.
Creating the Data Access and Business Logic Layers
You can create a data-access and business-logic layer for the database that you just created in several ways. You can customize these classes using your own business logic.
In this walkthrough, you will create a class that represents database entities. You can then add your own business logic to these generated classes. (You will not add business logic to the classes in this walkthrough.)
In this walkthrough, you will use Language Integrated Query (LINQ) to work with data. LINQ applies the principles of object-oriented programming to relational data. It provides a unified programming model for querying and updating data from different types of data sources and extends data capabilities directly into the C# and Visual Basic languages. For more information about LINQ, see LINQ (Language-Integrated Query).
You will use LINQ to SQL classes as the data-access layer. You will use the Object Relational Designer window in Visual Web Developer to generate entity classes that represent the data.
Mapping the Tasks Database to a SQL Data Context Class
To begin creating the data-access layer, you add a typed dataset to the project.
To create a class for the Tasks table
If the Web site does not already have an App_Code folder, right-click the project in Solution Explorer, click Add ASP.NET Folder, and then click App_Code.
Right-click the App_Code folder and then click Add New Item.
The Add New Item dialog box is displayed.
Under Visual Studio installed templates, select the LINQ to SQL Classes template and rename the file Tasks.dbml.
The Object Relational Designer window is displayed.
In Server Explorer, drag the TasksList table into the Object Relational Designer window.
Save the Tasks.dbml file.
Visual Web Developer creates the Tasks.dbml.layout file in the App_Code folder under Tasks.dbml. It also creates either Tasks.designer.cs or Tasks.designer.vb, depending on what programming language you are working with.
In Solution Explorer, open the Tasks.designer.cs or Tasks.designer.vb file.
Notice that the code contains classes named TasksDataContext and TasksList. The TasksDataContext class represents the database, and the TasksList class represents the database table. The parameterless constructor for the TasksDataContext class reads the connection string for the database from the Web site's configuration file (Web.config).
Open the Web.config file.
Notice that a connection string to the Tasks database has been added in the connectionStrings element.
Close the class file and the Web.config file.
Creating and Configuring a LinqDataSource Control
Now that you have a database table and classes that represent database entities, you can use a LinqDataSource on an ASP.NET Web page to access the database. The LinqDataSource control makes LINQ available to Web developers through the ASP.NET data-source control architecture.
The LinqDataSource control creates the code for selecting, inserting, updating, and deleting objects in the database. These classes can be called by business logic to perform database functions and apply business-logic rules.
To create and configure a LinqDataSource control
Open or switch to the Default.aspx page.
Switch to Design view.
From the Data tab of the Toolbox, drag a LinqDataSource control onto the Web page.
You can leave the ID property as LinqDataSource1.
In the LinqDataSource Tasks smart tag panel, click Configure Data Source.
In the context object list, select TasksDataContext and then click Next.
In the list, select TasksLists(Table<TasksList>), and then click Finish.
In the LinqDataSource Tasks smart tag panel, select the Enable Delete, Enable Insert, and Enable Update check boxes.
Save the page.
Notice that you did not have to specify any database commands for selecting the data.
Creating and Configuring a GridView Control
To create a user interface for the data that is made available by the LinqDataSource control, you can use various data controls. In this walkthrough you will add a GridView control to the page in order to view, update, and edit the data in the TasksList table.
To create and configure a GridView control
In the Default.aspx page, switch to Design view.
From the Data tab of the Toolbox, drag a GridView control onto the Web page
In the GridView Tasks smart tag panel, select LinqDataSource1 as the data source. (If you assigned a different name when you created the LinqDataSource control, use that name.)
In the GridView Tasks smart tag panel, select the Enable Editing and Enable Deleting options.
Press CTRL+F5 to run the page.
The page displays the data that you entered previously in the walkthrough, and it enables you to edit or delete rows.
This walkthrough has illustrated how to create the data-access and business-logic layer of an application by using the LINQ to SQL Classes template and the LinqDataSource and GridView server controls. You created a way for Web site pages to access data that is flexible and that is not directly tied to the presentation layer of the Web site.
The topic Walkthrough: Creating an Ajax-Enabled Data Application uses the LinqDataSource control to create an AJAX-enabled Web application that displays and updates information in the Tasks database.