Performance.Web - Use data-specific column types instead of data item templates whenever possible

Data item templates are not always required. Without unnecessary templates our web list editors will be rendered faster, especially in IE that has low tables rendering speed.
Here is some example code:

C#
using DevExpress.ExpressApp;  
using DevExpress.ExpressApp.Web.Editors.ASPx;  
using DevExpress.Web.ASPxGridView;  

namespace YourSolutionName.Module.Web {  
    public class RemoveCustomTemplatesFromGridColumns : ViewController<ListView> {  
        ASPxGridListEditor gridListEditor;  
        protected override void OnActivated() {  
            base.OnActivated();  
            gridListEditor = View.Editor as ASPxGridListEditor;  
            if(gridListEditor != null) {  
                gridListEditor.EnableGroupTemplate = false;  
            }  
        }  
        protected override void OnDeactivated() {  
            gridListEditor = null;  
            base.OnDeactivated();  
        }  
        protected override void OnViewControlsCreated() {  
            base.OnViewControlsCreated();  
            if(gridListEditor != null) {  
                foreach(GridViewColumn column in gridListEditor.Grid.Columns) {  
                    if(column is GridViewDataColumn && !(column is GridViewDataActionColumn)) {  
                        ((GridViewDataColumn)column).DataItemTemplate = null;  
                        ((GridViewDataColumn)column).EditItemTemplate = null;  
                    }  
                }  
            }  
        }  
    }  
}  

Take special note that XAF provides custom data and edt item and group ITemplate objects as part of the PropertyEditor creation for each column to deliver a generic way to control data validation, formatting, localization and other XAF features. They will be lost when this code is used, but perhaps you do not need them in certain scenarios.
Alternatively, to improve performance of large grids with a lot of records and columns you can do the following:

1. Create a new ListEditor using the ASPxGridView control as it is described in the How to: Implement an ASP.NET Web List Editor Using a Custom Control.
2. Implement a custom ViewItem based on a user control with the same ASPxGridView and show a dashboard View from the navigation as it is demonstrated at How to show custom forms and controls in XAF (Example).
   Options #1-2 are pretty similar and basically vary by the container where a pure ASPxGridView will reside.
   See Also:
   ASPxGridView very slow with 30 properties
   Group By panel problem