Returning Dataset to ASP.NET from .NET Component / Business Object Serialization
Yes. In ASP.NET you have two choices.
1. Code in the ASP.NET page
2. Code in the CodeBehind file, which is a class file.
The page and the CodeBehind file are rather intimately linked, as the page
will inherit from it. The upside of ASP.NET (or rather ADO.NET) is you have
the choice of coding an object that is strictly a forward only cursor
(DataReader). These are optimized by access type (ie, SQL Server is designed
for SQL Server only). The DataSet, which is a Recordset (plus much more -
can be a mini-relational database), is more full featured, but has more
baggage.
For remote data, you can serialize the dataSet into XML. .NET will actually
do most of the legwork for you when it comes to serialization. Since
Microsoft has already written much of the code in the Framework, it is
fairly well optimized.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Author: ADO.NET and XML: ASP.NET on the Edge (4Q 2001)
*************************************************************************
Think Outside the Box!
*************************************************************************
Quote:
> Is returning a Dataset to an ASP.NET page as a result of a .NET Component
> method call a performance 'nono'? Most of my recent application serialize
> and
> results to the Presentation tier as XML. Will .NET finally give me the
> ability to
> return Data Objects to my ASP code without horrific performance
degradation?
> NOTE: I am also looking for a .NET substitute for using Property Bags to
> serialize
> data between Business Objects. Any ideas or references would be
appreciated.
> Thanks in advance,
> Jose de Castro
> System Analyst
> Idagen Consulting
