Interacting with Databases Using ASP.NET 2.0 with the Microsoft Data Access Application Block - Summary
(Page 6 of 6 )
I just wanted to let you know that the code in this article is neither suitable for all scenarios nor is it the best implementation for every application. For example, you can develop another wrapper class by extending the existing Data Access Application Block to make your code reusable in several other applications.
If you wanted to use it throughout the machine, you can make it strongly signed and place in GAC as well. Further, you can integrate with COM+, .NET Remoting, Web services and so on, by properly implementing serialization for your wrapper. It all depends on the factors you would like to consider while developing an application.
You can also observe that I didn’t even use/execute stored procedures in any of the methods. In my upcoming contributions, we shall look into the most used advanced 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!
The entire source code for this article is available in the form of a downloadable zip file. The solution was developed using Microsoft Visual Studio 2005 Professional Edition on Microsoft Windows Server 2003 Enterprise Edition together with Microsoft SQL Server 2005 Developer Edition and Microsoft Enterprise Library for .NET Framework 2.0 (January 2006 version). I didn’t really test the solution with any other/previous editions. If you have any problems in executing the solution, please post in the discussion area.
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. |
