Skip to main content

ASP.NET and CompositeDataBound



CompositeDataBound Class:
                                                          It’s abstract base class. It implements INamingContainer interface.

GridView Control:
                             GridView generates data in tabular format. It provides easy paging, sorting, and editing.

GridView      => Rows (GridViewRow)         => Cells (DataControlFieldCell)
                        => Columns (DataControlField)

When a row is created InitializeRow() is called that creates cell and calls InitializeCell method that creates DataControlFieldCell. Columns class inherits form DataControlField and overrides the InitializeCell method.

TemplateColumn, BoundColumn etc inherit from DataControlField to create DataControlFieldCell.

    IStateManager
    IDataSourceViewSchemaAccessor
O------ DataControlField
                   +-->TemplateField
                   +--> HyperlinkField
                   +--> ImageField
                   +--> BoundField
                                   +--> AutoGenrateField
                                   +--> CheckBoxField
                   +--> ButtonFieldBase
                                   +--> ButtonField
                                   +--> CommandField



RowCreated and RowDatabound events are used to programmatically alter the Row and Cell Style.


DetailsView Control:
                                                Shows Single record from DataSource. It allows edit, Delete and insert. AllowPaging property allows auto paging. Formatting capabilities are same as GridView.

FormView Control:
                                      It’s just like the DetailsView to display a single record. It allows user defined templates for inserting, updating and Deleting.

Select
Edit
Delete
New
Auto Generate Edit / Delete
Edt/New Templates
Tabular Display
Form Display
Grid of Items View
Persists View State
Custom UI
2
Table/HTML Table






.
.



3
Repeater











4
XML Control






.
.r



6
DataList


cn








6
DetailsView







.



6
FormView

cn
cn
cn



.



7
GridView






.




9
ListView



























Control
Functionalities
2
Table/HTML Table
Tabular + Form Display
3
Repeater
Item Select + Custom UI + Persistence
4
XML Control
Tabular + Form® + CustomUI + Grid of Items
6
DataList
Item Select + Edit + Delete + Edit/New Templates + Persistence
6
DetailsView
Form View + Edit + Delete+ New + Auto Generate  Edit/New/Delete Button+ Persistence
6
FormView
Form View + Edit + Delete+ New + Auto Generate  Edit/New/Delete Button+ Persistence
7
GridView
Form View + Edit(cn) + Delete(cn)+ New(cn) + Edit/New Templates+ Persistence
9
ListView
Select Item + Tabular Display + Form Display + Custom UI + Grid of Items View + Edit + Delete + Edt/New Templates + New + Auto Generate Edit / Delete + Persists View State


cn Operation supported by Command Name (“edit”, “new”, “delete”)
® r Readonly

Labels:

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 »