Thanks for the quick response. I will try this approach.

Hi

 I think Infragistics still doing research on this issue best for u is to bind to object rather than objectcontainerdatasource.

It looks somthing like this

IList<DomainObject> BindInfragisticsGrid

{

set

{

UltrawebGrid.DataSource = value;

UltrawebGrid.DataBind();

}

}

If you bind manually like this then only you will be able to use paging and server side sorting.

Hello All,

I downloaded the latest preview of WCSF (Feb 2008, for 3.5 and VS 2008) and started from the ObjectContainerDataSource example that is provided in the package. I indeed was able to verify the following issues (please see screenshot attached):

1) At design time, the control will not automatically pick the datasource schema (where as stock asp:GridView does)

2) Paging will not work - initially the grid will be displayed, but page 2 will cause errors, whereas the same code will function in asp:GridView

This is logged and being looked into, and I do assure you that we mean that seriously, it is just that WCSF has not been our target of attention up until recently and this will certainly take time. The newly introduce ObjectContainerDataSource will also be something that we will be working on. I will let you know once we have progress.

Meanwhile, I can join the suggestion above and suggest trying binding with code directly against the DataSource property, as opposed to declaratively using DataSourceID when dealing with ObjectContainerDataSource/MVP/WCSF.

Please, excuse us for the inconvenience while we are working on support for this.

I suggest try using regular collection object and see what can be possible with infragistic objectcontainerdatasource and infragistic work well only for first bind but it is big problem after that esp. for custom serverside Paging and Sorting.Infragistics should try getting this work

Infragistic version 1 2007 CLR2.0