Skip to main content

ASP.NET Working With Data-Bound Web Server Controls

Suppose we have:
List<Car> vCars = new List<Car>();

There are three types of databound controls: Simple databound controls(List, AdRotater), Composite data bound controls(GridView, DetailsView, FormView that inherit from CompositeDataBoundControl), and Hierarchal data bound controls (TreeView, Menu).

 



DataBoundControl has a DataBind method that can be used when data is ready. It calls DataBind for child controls as well. Page.DataBind() will call DataBind for all child controls.

Using DataSource Objects:
                                      BaseDataBound control exposes DataSource property that accepts objects that implement IEnumerable, IListSource, IDataSource, or IHierarchalDataSource. DataSourceID accepts ID of SqlDataSource. If both specified DataSourceID takes precedence.
GUI based data sources DataSourceControl or HierarchalDataSourceControl implement IDataSource and IListSource interface.
 

GUI Based Data Source
Description
AccessDataSource
MS Access (.mdb)
SqlDataSource
Open Database Connectivity(ODBC), Object Linking and Embedding Databases(OLEDB), SQL Server, SQL (.mdf)
XmlDataSource
XML file within your project. Use XPath for a subset, or XSL Transform can also be used.
ObjectDataSource
Any object implementing IEnumerable, IListSource, IDataSource, IHierarchalDatasource can be used. Like a collection, DataSet, DataTable can be used. 
SitemapDataSource
A valid sitemap file at root of the application.

Mapping Fields to Templates:
                                                Only controls that support templates. Templates have no default interface. Controls only provide binding support. Developer provides UI for templates. Templates can also contain ASP.NET Binding commands. Controls that support templates are GridView, DetailsView, and FormView.

Template
Description
HeaderTemplate
Optional. Header at the top of control.
FooterTemplate
Optional. Footer at the bottom of the control.
ItemTemplate
ItemTemplate is rendered for each row of the DataSource.
AlternatingItemTemplate
Optional. Just like ItemTemplate, But for each odd index.
SelectedItemTemplate
Optional. Template for Seleted Item Template.
SepratorTemplate
Optional. Template to seprate Item and alternate item.
EditItemTemplate
Optional. Edit mode template.



Using the DataBinder Class:
                                                DataBinder class provides a static method called Eval to access Data. Eval uses reflection, looks for the item in DataItem and retrieves the value.

<#% Eval(“VIN”) %>
An overload also provides format capabilities.
<#% Eval(“VIN”, “{0:C}”) %> //Currency

Eval provides read only access.
ASP.Net 2.0 provides Bind that allows updates as well.
<#% Bind(“VIN”) %>
<#% Bind(“VIN”, “{0:C}”) %>
GridView, DetailsView, and FormView only support Bind. The control must have a user-defines ID set, in order to user Bind.

Labels:

Comments

Post a Comment

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...
Post a Comment
Continue Reading »

Concept of App Domain in .Net

Creating Application Domains: Application domain is just like process, provides separate memory space, and isolates from other code. But it’s quite light weight. It also provides the following advantages: 1-       Reliability : If a domain crashes, it can be unloaded. Hence doesn’t affect the other assemblies. 2-       Efficiency : Loading all assemblies in one domain can be cumbersome and can make the process heavy but Appdomains are efficient in this manner. Important properties of AppDomain: ApplicationIdentity , ApplicationTrust , BaseDirectory , CurrentDomain , DomainManager , DomainDirectory , Evidence , FriendlyName , ID , RelativeSearchPath , SetupInformation , ShadowCopyFiles . Important methods of AppDomain: ApplyPolicy , CreateCOMInstanceFrom , CreateDomain , CreateInstance (Assembly). To create an AppDomain: AppDomain adomain = AppDomain.CreateDomain(“D”); To execute an assembly:...
Post a Comment
Continue Reading »

Asynchronous Execution in ASP.NET

Asynchronous Execution: Two ways either implement IHTTPAsyncHandler interface or in ASP.NET 2.0 set <%@ Page Async=”true” %>. The second option implements IHTTPAsyncHandler interface automatically for the page when parsed or compiled. AddOnPreRenderCompleteAsync ( new BeginEventHandler(BeginTask), new EndEventHandler(EndTask)); AddOnPreRenderCompleteAsync() shoud be called in Page_load. The BeginEventHandler and EndEventHandler are delegates defined as follows: IAsyncResult BeginEventHandler( object sender, EventArgs e, AsyncCallback cb, object state) void EndEventHandler( IAsyncResult ar) AsyncProcess starts and completes between PreRender and PreRenderComplete. Other way to perform Async Task is using AsyncPageTask structure. It also allows multiple tasks to execute simultaneously. void Page_Load (object sender, EventArgs e) { PageAsyncTask task = new PageAsyncTask( new BeginEventHandler(BeginTask), new EndEventH...
Continue Reading »