Jason,

We typically bind the WebDataGrid to a SQLDataSource control.  I am open to learning a new binding mechanism if we can find something that works without having to rewrite the entire project to MVC.

Thanks, -Rob

Rob - how are you binding your data to the WebDataGrid?  Do you use Datasets in code-behind?  That's where the igGrid in Ignite would not be a good replacement ... it's looking for a client side data source unless you are doing something in MVC.

Rob,

Being that the Ignite UI grid is a client side grid, you can use it in your ASP.NET applications if you wish to.  For case CAS-128340-X0X4J0, Zdravko has already responded that this is fixed internally and will be in the next service release.

Let me know if you have any questions.

Jason, the UI elements on the Ignite grid are definitely superior to what we have in WebDataGrid.  The end-user experience is much better.

If the Ignite grid could be used with WebForms, then I might prefer it for new development.

Alan, FYI, I just submitted another high profile bug in the latest build of 13.2.  WebDataGrid and WebMaskEditor are broken in IE11.  You can't edit numeric fields.  Case: CAS-128340-X0X4J0

There are always more features we can add ... there are hundreds ... we can chase features forever ... but you get to a point where the grid has 80% of the features that customers have asked for, and after that, it's small features for very specific needs.  That's why we added the user voice for feedback, so we can get another input for features needs, figure out what we are missing in that 80%.

What else do you need besides a UI on top of the CRUD?  And for this UI on the CRUD, would the work we did on the HTML / MVC grid satisfy what you are after:

http://www.igniteui.com/grid/basic-editing

Let me know,

Thanks

Jason