how about converting the list of customers to a list of customers from a database using linq to sql.

i am new to mvc and trying to create a maintenance form.

your response would be a great help

thanks

This is because the in the CustomerController.cs -> FillGridData() function, grid was bind to criteria before _grid.Pager.Init(totalRows) is called. The fix does change the CurrentPage value in Pager but not the criteria.PageIndex value. In result, a error message shows (There are no customers that match specified criteria).

To fix this problem, just insert this line after _grid.Pager.Init(totalRows):
criteria.PageIndex = _grid.Pager.CurrentPage;

Now, the last page will always shows regardless what ur Pager.CurrentPage value is.

Thanks.

This is really a very good component. Thanks to shared it for everyone.

I noticed an issue in the demo page: click on the search button several times causes the grid to show up multiple times within the page.

Any idea why ?

Thanks.

<div style="clear: both;"/>

Seems like IE doesn’t know how to handle self-closing div tags. It was ignoring the closing of the div, so from IEs perspective – AJAX was returning malformed HTML – which resulted in the multiplicity.

Changing the line to:

<div style="clear: both;"></div>

fixes the issue and I will include it in upcoming update.

A simple google search showed that there are other people who experienced the same problem. For ex. here:
http://blog.seanmcg.com/?p=176

This specific design works very well for in-memory objects, but not well with database driven apps. At the moment, I’m trying to integrate this into a multi-layered application built on of S#arp Architecture. The EntityCriteria that builds the query that allows for all of the paging, sorting, and searching works off an in-memory object. When integrating with NHibernate, the code needs to be changed to build an NH query accordingly so that only the data that’s necessary for this page, with these search parameters, in this order are fetched. I’ve yet to do this and it’s sitting on my todo list.

Furthermore, the separation of classes in various namespaces and layers get more complicated. At the moment, I’ve appended the Grid, IGrid, Pager, SearchForm, and Sorter classes with “ViewModel” and put them in my Web.Controllers project in a \ViewModels\Shared folder. I’ve striped out the binders from Utils and put them into GridBinders.cs, and I renamed GridStateService to GridStateManager and put this all in \Grid in the same project. The other utility classes landed in my Utility project.

Then there’s the challenge: where to put the EntityCriteria and its inheriting classes. They may belong in the Core (Domain) project, which is where the domain entities reside, but with the data access modifications mentioned above, they really need to be with the data repositories. So a natural fit seems the Data project. The Controllers should also access them via an Application Service, rather than directly. This poses the separation of concerns and loose coupling challenge. Application Services should have Data related objects injected (persistence ignorance), and Controllers should have Application Services injected, which begs the question, how do you expose the functionality of EntityCriteria that reside in the Data project? For example, the SortDirection enum will need to be moved or duplicated.

I’m currently toying with some ideas for using interfaces and such to see what I can figure out. This is my very next todo. Then I’ll have to spend some time unit testing this infrastructure.

I really like the base design, thanks for sharing, and please feel free to discuss implications such as the ones I’ve mentioned.

I personally think you should package the code components of this project as a DLL, with a guideline of how to create the ASCX / ASPX file required to have a grid. The JS and CSS files could be packed as required components to import.

All in all, this is fantastic and could become a huge MVC component in the open source community. Thanks for taking the time to code it.

Thanks a lot.

2. How to process multiple forms in the same page? There are small login box and search box in my page, but only the first form could be submit, how to submit second or third form in the same page?

Thanks you again.