Most dynamic Web applications are created for the sole purpose of making money on the Web.
Let’s face it: why would you go through all the work of creating a dynamic Web application if you don’t plan to make money through it? Sure, companies employ dynamic intranet sites and there are still some — although very few — free Web applications you can use.
In the real world, however, dynamic Web applications are created in an attempt to make money by allowing site owners to sell merchandise on the Web. Providing users with the capability to add items to a virtual shopping cart as they browse through your Website is still very much a business that commands good money. Companies such as VeriSign, Paypal, WebAssist, and LinkPoint charge to provide developers with the capability to add shopping cart functionality to their own Websites. But why pay $300-$400 for a solution that someone else already built, when you can build one just as easily yourself utilizing new technology in ASP.NET, for free?
This article will allow you to develop and implement your own shopping cart utilizing a Session, a DataGrid, and the
DataTable class of the
DataSet object. Through this article, you’ll learn to:
- Build a user interface using ASP.NET Web Server Controls
- Dynamically construct a DataTable depending on user interaction
- Bind the dynamically constructed DataTable to a DataGrid
- Allow the user to remove items from the cart freely
- Keep a running cost total of items within the cart
At the end of this article, you’ll have a fully functioning shopping cart, and you’ll have gained a thorough understanding of DataTables, DataGrids, and Session Variables. Download a complete demonstration of the final product here.
This project is separated into five parts:
- Building the user interface
- Building the DataTable structure
- Adding items to the cart
- Keeping a running total
- Removing items from the cart
Step 1: Building the Shopping Cart User Interface
The user interface or UI for the application is quite simple. In fact, most of the interaction will occur within the DataGrid, but the UI does include some key components that the user will be interacting with:
DropDownListWeb control that will display the products that we’ll offer. The cost of each item will be associated with the value of the
DropDownListWeb control for simplicity’s sake.
TextBoxWeb control that offers the user the ability to adjust quantities
ButtonWeb control to add to the cart
DataGridthat will contain the cart’s contents
Labelcontrol that will display to the user a running total in terms of price
Now that you have an idea of what the UI will display, let’s add these components to the body of an HTML page. Using Dreamweaver MX, we’ll create a new page and add this code into the
<body> tag of the page:
<asp:DropDownList id="ddlProducts" runat="server">
<asp:textbox id="txtQuantity" runat="server" /><br><br>
<asp:Button id="btnAdd" runat="server" Text="Add To Cart"
<asp:DataGrid id="dg" runat="server" /><br><br>
<asp:Label id="lblTotal" runat="server" />
The code is actually quite simple and needs very little explanation. Basically, a hard-coded
DropDownList control (
TextBox control (
txtQuantity) is added so that the user can modify quantities. Next, a
Button control (
btnAdd) is added with the text “Add to Cart”. The
onClick event associated with the Button control will call the
AddToCart() subroutine, which will be created in the next section.
dg) is added which will be used to bind to the dynamically constructed
DataTable. Remember, the
DataTable will be constructed in code, and bound to the
DataGrid for presentation to the user. We’ll add a button column to allow the user to remove a specific item if he or she wishes a little later. Finally, we’ll add a
Label control (
lblTotal), which will be used to display to the user a running total of the items within the cart.
Step 2: Building the
If you’re familiar with DataSets
, then you know that DataTables provide you with a way to dynamically create a purely memory-resident representation of a database table. Typically, you’d fill a DataTable
In a DataTable, columns are represented by the columns property, and rows are represented by the rows property. Thus, DataTables will be the perfect choice for the creation of our shopping cart. We can build the columns just as we would within a database, using the columns property of the
Rows property. With the DataTable built, we can then bind the DataTable to a DataGrid to display the results in an intuitive manner.
Because DataTables contain rows and columns, you will be able to effectively mock the structure of a conventional database table. The rows will be added to the DataTable as the user adds items to the cart. For now, we’ll need to construct the columns that will serve as the categories for the row items. In order for the cart to function correctly, we’ll need to add the following columns with a corresponding data type:
You’re probably wondering how data types, auto increment, and uniqueness will be set programmatically. Remember, DataTables contain column and row properties. Some of those properties include the ability to set the above mentioned items, just as you would a traditional database table. You’ll also notice that the
DataTable contains a column for ID. Technically, this column has nothing to do with the shopping cart, but it will have a lot to do with keeping the items in the cart unique, and will allow us to establish a primary key if we ever want to create a relationship with another DataTable.
For now we just want the structure of the DataTable built when the page loads for the first time. We don’t want to actually start to define rows until the user selects an item to add to the cart.
To begin building the cart’s structure, add this code into the head of your page:
Dim objDT As System.Data.DataTable
Dim objDR As System.Data.DataRow
Private Sub Page_Load(s As Object, e As EventArgs)
If Not IsPostBack Then
objDT = New System.Data.DataTable("Cart")
objDT.Columns("ID").AutoIncrement = True
objDT.Columns("ID").AutoIncrementSeed = 1
Session("Cart") = objDT
Looking at the code, you can see, that the
makeCart() function is called only when the page is loaded for the first time. This is the reason for the IsPostBack check.
makeCart() function, we’ll add the code that defines the actual structure for the DataTable and its columns. First, we add a column to the DataTable named
ID, assigning it the data type for integer. We assign the property for
True, and begin the seed at 1.
Next, add three more columns to the DataTable for
Cost, assigning them the data types for integer, string, and decimal respectively. Finally, the DataTable is added into a
Session conveniently named “
Cart“, for storage.
That’s it! If you think about the structure of a database table and then consider the structure and code for the DataTable, they begin to resemble each other conceptually. The next step involves adding items to the cart, which is no harder than defining new rows for the DataTable.
Frequently Asked Questions (FAQs) about .NET Shopping Cart with DataTables
How can I add more products to the .NET shopping cart?
Adding more products to the .NET shopping cart involves modifying the DataTables. You need to add more rows to the DataTables, each representing a new product. Each row should contain the product ID, name, price, and quantity. After adding the new rows, you need to update the Session variable to reflect the changes in the DataTables.
How can I remove a product from the .NET shopping cart?
To remove a product from the .NET shopping cart, you need to find the corresponding row in the DataTables and delete it. After deleting the row, you need to update the Session variable to reflect the changes in the DataTables.
How can I update the quantity of a product in the .NET shopping cart?
Updating the quantity of a product in the .NET shopping cart involves modifying the corresponding row in the DataTables. You need to find the row with the product ID and change the quantity. After updating the quantity, you need to update the Session variable to reflect the changes in the DataTables.
How can I calculate the total price of the products in the .NET shopping cart?
To calculate the total price of the products in the .NET shopping cart, you need to iterate through all the rows in the DataTables and sum up the product of the price and quantity of each product. The total price should be stored in a separate variable.
How can I display the products in the .NET shopping cart on a webpage?
Displaying the products in the .NET shopping cart on a webpage involves binding the DataTables to a GridView control. The GridView control will automatically generate the columns and rows based on the structure of the DataTables.
How can I save the .NET shopping cart to a database?
Saving the .NET shopping cart to a database involves converting the DataTables to a format that can be stored in a database, such as XML or JSON. After converting the DataTables, you can use the standard database operations to insert the data into the database.
How can I load the .NET shopping cart from a database?
Loading the .NET shopping cart from a database involves retrieving the data from the database and converting it back to DataTables. After converting the data, you can update the Session variable to reflect the changes in the DataTables.
How can I handle errors in the .NET shopping cart?
Handling errors in the .NET shopping cart involves using try-catch blocks to catch any exceptions that may occur during the operation of the shopping cart. The caught exceptions should be logged for debugging purposes and a user-friendly error message should be displayed to the user.
How can I secure the .NET shopping cart?
Securing the .NET shopping cart involves implementing various security measures, such as using HTTPS for all communications, validating all user inputs, encrypting sensitive data, and using secure session management.
How can I optimize the performance of the .NET shopping cart?
Optimizing the performance of the .NET shopping cart involves various techniques, such as minimizing the number of database operations, using caching to store frequently accessed data, and optimizing the code for efficiency.