Hi,

Itried it and it works grate .

I have onle one small problems:

One of my tables contains 1500 rows and 50 columns, in aresults the grid has large viewstate (more than 1M...).

When disabaling the viewstate it stop to function and raise javascript errors on paging, update ext.

Does someone have any idea how to solve it ?

Can we have a little more information such as what kind of grid you are using and you are binding your data to it.

Cheers,
Jon Sharratt

I'm using the default grid that the template generated.

I copied it to new folder and gave the folder the table name.

The only changed I did in the ListDetails.aspx page is to decrease the number of then columns:

<asp:DynamicGridView ID="GridView1" runat="server" DataSourceID="GridDataSource"

AutoGenerateSelectButton="True" AutoGenerateEditButton="True" AutoGenerateDeleteButton="True"

AllowPaging="True" AllowSorting="True" EnableQueryStringSelection="True" OnDataBound="OnGridViewDataBound"

OnRowEditing="OnGridViewRowEditing" OnSelectedIndexChanging="OnGridViewSelectedIndexChanging"

AutoGenerateColumns="False" >

<Columns>

<asp:BoundField DataField="ID" HeaderText="#" SortExpression="ID" />

SortExpression="FoodCode" />

SortExpression="Description" />

SortExpression="KeyWords" />

SortExpression="FoodCatID" />

SortExpression="Short_desc" />

</Columns>

<PagerTemplate>

<uc1:GridViewPager runat="server" />

</PagerTemplate>

<EmptyDataTemplate>

<AlternatingRowStyle CssClass="even"></AlternatingRowStyle>

</asp:DynamicGridView>

<asp:LinqDataSource ID="GridDataSource" runat="server">

<WhereParameters>

<asp:DynamicControlParameter ControlID="FilterRepeater" />

</WhereParameters>

</asp:LinqDataSource>

Hi nati28,

the ASP.NET 3.5 Extensions preview is an early preview version of the Dynamic Data feature and might not have all of its behavior optimized. In addition, Dynamic Data controls do not currently function with viewstate turned off in edit scenarios. We are working on addressing this issue.

On a side note, you are using BoundFields in your columns collection. To take advantage of the field template feature of Dynamic Data you should be using DynamicFields instead. 

Do you see the view state changing size as you change the number of displayed columns, or does it make no difference?  e.g. if you try 1, 2, 5, 10, 50 columns, how does it affect the size?

Also, are you displaying all the rows at once, or are you using paging?  e.g. If you only display 10 rows at a time, you should get less much view state than if you display them all.

Note that all this is probably not specific to Dynamic Data, and I suspect you'd see similar behavior with a regular GridView & LinqDataSource.

David

1. Table with about 5 columns and 10,000 rows.
2. using the default templates (with paging...)
3. the page size is 6M !

Nati,

could you write a page that uses a regular GridVIew to display your table and compare how much view state you are seeing without Dynamic Data being involved? Then we would be better able to isolate your problem.

Strange, I'm not seeing this.  I see the ViewState get larger as I add more columns.  Does your page also contain some filters (i.e. drop downs)?  Those also contribute to the view state, and for foreign keys into tables with lots of rows they can make a big difference.  To do a valid comparison between the DynamicGridView and the regular GridView, you would need to reduce the default page to only have the DynamicGridView and LinqDataSource, and not any of the other things (filters, detailsview, etc...).

David