Devexpress 9.2.6
Alternative for DevExpress AgDataGrid. They have 4 components in their suite. Version 9.2.6 was released a week ago not a single fix for Silverlight.
Can you please let me know what your experiences are with the AgDataGrid 9.2, Telerik's and maybe other vendors like CompentOne. Prefereably something as extensible as the Silverlight Toolkit datagrid but that already can do basic things, like grouping, filtering, sorting, setting conditional row coloring. I have found that the AgDataGrid is trying to mimic their XtraGrid controls to closely and really messed up binding (FieldName, EditValue nightmare) and many other issues that I have logged with them and has been added as suggestions to future releases.
Esite, Sure you've got to create a DataTemplate, and I agree with you on the binding issue. Of those 10 issues that were asked, were all of them resolved in a timely manner? DevExpress have more then 4 Components for Silverlight, AgRichEdit, AgMenu, AgDataGrid, AgEditors (Which contain over 10 controls), AgBookControl, AgTransitionControl, AgLayoutControl (the best in the business), AgXpo (silverlight version of their XPO framework) and on and on. Also in 9.2.6 there were over 5 fixes and feature implementations for Silverlight. If you look at the What's Included & New link in the ClientCenter it will show you. They're fully committed to silverlight, if they weren't, they wouldn't be developing controls, they're developing a beta of the XtraScheduler suite which should be ready for 9.3, and their controls should be out of beta in 9.3. Their Silverlight controls have been available for over a year now, and were introduced as betas in 8.2.
I don't agree with a component vendor simply rushing controls out the door for the sake of being first to market. Look at the time invested for people to get controls ready for SL2 only to have SL3 released 8 months later. You've then got to recompile your controls to SL3, put it through the rigorous testing and have it ready, and who knows, might need some rework. Esite, I've used ComponentOne, Telerik and the AgDataGrid, and have to say, apart from the Binding 'issues' you're talking about, the AgDataGrid takes the cake for all of the Silverlight Grids. But as the AgDataGrid is still in beta, you can expect to see these 'issues'.
I don't agree in rushing a product into commission just for the sake of being in the market first, and I believe DevExpress share the same values. One thing you have to remember is that Silverlight 2+ is very very young. 18 Months to be exact, so being on the edge of technology, expect to see some teething problems. The suggestions on the Path binding attributes are good suggestions, and will obviously be implemented., but what's so wrong with using the EditValue.Person.FirstName context?? Esite, Sure you've got to create a DataTemplate, and I agree with you on the binding issue. Of those 10 issues that were asked, were all of them resolved in a timely manner? DevExpress have more then 4 Components for Silverlight, AgRichEdit, AgMenu, AgDataGrid, AgEditors (Which contain over 10 controls), AgBookControl, AgTransitionControl, AgLayoutControl (the best in the business), AgXpo (silverlight version of their XPO framework) and on and on.
Also in 9.2.6 there were over 5 fixes and feature implementations for Silverlight. If you look at the What's Included & New link in the ClientCenter it will show you. They're fully committed to silverlight, if they weren't, they wouldn't be developing controls, they're developing a beta of the XtraScheduler suite which should be ready for 9.3, and their controls should be out of beta in 9.3. Their Silverlight controls have been available for over a year now, and were introduced as betas in 8.2. I don't agree with a component vendor simply rushing controls out the door for the sake of being first to market. Look at the time invested for people to get controls ready for SL2 only to have SL3 released 8 months later.
9.2.6 Clear Browser Cache
You've then got to recompile your controls to SL3, put it through the rigorous testing and have it ready, and who knows, might need some rework.