Developing ASP.NET 2.0 Applications with the Microsoft Data Access Application Block - Developing the code
(Page 5 of 5 )
Up until now, we configured the enterprise library to work with our application. Now, it is time to write some code and access the data in the database. To make this demonstration simple, I am going to work with the GridView control. Let us walk through the steps now:
- Drag the GridView control from the toolbox and drop it within a "div" pair. The code should look something like the following:
<%@Page Language="VB" AutoEventWireup="false" CodeFile="Default.aspx.vb" Inherits="_Default" %>
<!DOCTYPEhtml PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<htmlxmlns="http://www.w3.org/1999/xhtml" >
<headrunat="server">
<title>Untitled Page</title>
</head>
<body>
<form id="form1" runat="server">
<div>
<asp:GridView ID="GridView1" runat="server">
</asp:GridView>
</div>
</form>
</body>
</html>
- Now, go to the code window (by pressing F7) and modify the code in such a way that it looks like the following:
ImportsSystem.Data
ImportsMicrosoft.Practices.EnterpriseLibrary.Data
PartialClass _Default
Inherits System.Web.UI.Page
Protected Sub form1_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles form1.Load
Dim db As Database
db = DatabaseFactory.CreateDatabase("AdventureWorks")
Dim dt As DataTable = db.ExecuteDataSet(CommandType.Text, "select * from HumanResources.department").Tables(0)
Me.GridView1.DataSource = dt
Me.GridView1.DataBind()
End Sub
EndClass
You must note that in the above code, I am importing the enterprise library at the top. The statements containing words like "database," "databasefactory," "createdatabase" and "executedataset" are nothing but the existing classes/routines available in the enterprise library. These are not at all related to ADO.NET. You can simply consider them to be user-defined classes/routines within the enterprise library. For a full list of classes/members, I suggest you to go through the documentation related to the enterprise library.
Finally press F5 to execute the application and to give you the list of all departments existing in the AdventureWorks database.
In my upcoming contributions, we shall look into the most used routines in the Data Access Application Block (along with accessing stored procedures). Don’t forget to check back or sign up for a newsletter to notify you!
Any feedback, suggestions, bugs, errors, improvements etc., are highly appreciated at jag_chat@yahoo.com.
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
