ASPxGridView Product Review

I have been using one of your competitors for quite some time now and I have been quite OK with it. Performance has not been lightning fast but it has been very easy to use this grid. Once I saw your claims that the new DevEx grid is very quick I decided to give it a try. The example you refer to is very vague and does not help at all – it just has some animated GIFs and does not really show anything … just plain marketing. Once I have tried your grid in my actual pages it did not help anything – it is NOT faster and output is NOT smaller than what I use now, performance is even a bit worse than what I have now. Please reconsider your marketing messages as you are doing yourself damage with examples using animated GIFs and hard-coded values without any real comparison. How exactly are you doing your comparisons? Are you using the same settings and operations? It is probably the case that you have optimized your grid and put the other "market-leading" grids in "slow" mode…

I think your grid is great, except for one *major* issue. The reliance on using XPO for many of the advanced features. We already use nHibernate so don't need XPO but had to cancel our order for your grid when it was discovered we could not do things like server side paging. This is a disappointment as the overall quality of the grid is very high.

Hi Mehul, Can you point me to some documentation on how to implement server side paging and grouping without using XPODataSource.

Its discusting how these people whinge and point fingers without actually posting facts of their testing, and if they are so sure of a "SLOW" mode coded in why not purchase the Source Code??  

How about Adam posts his actual tests before flaming the Marketing Campaign and Steve Orr's review??

I think here is the catch

DevExpress offers the source code as part of a subscription.

now, why can't the competitors catch up?

this is mind bugling.

now, you try incorporating the grid to your project, just because it takes time to configure the grid properly and you end up frustrated, does not mean the grid is not good enough.

instead of incorporating the grid to your pages, why not make a separate page and do the comparison? or at least have the wit to read the reviews before jumping to any conclusion?

-but thats just me

I am currently testing your grid against one of your competitors. First, I used a small dataset (5 records) and was amazed at how fast it was compared to the competitor. I then moved to one of our production databases and tested it on a larger recordset with a different competitors grid on the same page. It was still faster. I do not know how you guys do it, but i am really impressed.

Also, your grid was intuitive to set up. It seems pretty close to the standard asp.net gridview control in terms of setup, just way better. Setting up paging was incredibly easy.

The footprint of your grid compared to the competitors grid in production was amazingly small.

I think your grid is fast. I do not know what that Adam guy is talking about.

Thank Mehul. I was aware of the IListServer requirement to get it to work. As you say this is not a trivial task and I started to try and get it to work but it was too much without proper documentation. Throwing in a few XPO components here and there for large datasets is not really an option as all that does is make our nicely structured architecture messy. I would recommend cleaning up this whole IListServer stuff so it is easy to get virtual paging, grouping etc working with non-XPO datasources and you will make many people very happy.

I have to leave here my comment.

The moment I decided to buy a 3rd party web grid component, I started looking at most of the available grid in the market.

That includes Telerik, Infragistics and such.

My opinion is: aspxgridview is far the best product available in the market.

Its a brand new one, so its expected to have some stuff to improve, yet it presents lots of amazing features, not necessarly only related to performance.

Performance is great indeed, for sure no other product would beat it. All the tests Ive done were loading large datasets and I can say most grids just stuck where as aspxgridview behaved like a breeze.

Devexpress has been doing an excelent job, maybe Adam is speaking as a competitor, thats the only reason I see to post such a comment!

I am evaluating the XPO or server mode for one  of my clients who is currently using the DevExpress in the classic mode.

I liked the XPO samples they are very fast as claimed by the sales.  However, the biggest limitation I find is that XPO works great as long as you have a simple table structure or a simple view. The moment you have a complex query , neither XPO nor the LinqServerMode works. It can't even support complex primary key. Not sure why the primary key is required for read-only grids.  

The ASP.NET gridview and linqdatasource works like a charm without the primary key criteria

Anybody has deployed DevExpress grid with a complex query with 6-7 joins and no primary keys ?