While testing the WPF grid, I noticed that the size of the recordset being bound severely impacted the rate at which it populated, especially once it has been styled and themed. I am not talking about thousands of records either. The difference betweem 20 records and 500 records was exponential. My solution? Revert to an old VB4/5/6 trick and make the grid invisible, bind it, and then make it visible again.
I would think in this day and age, the bind method would turn off all the paint events until after it was done populating and I would not have to resort to such a hack.
Just saying.
What about in the VS 2008 environment, has anyone noticed slower compilation times as a result of using the grid?
Thanks,
Wade
VS2008 seems slower compiling no matter the type of app, regardless of the grids inclusion. I am not sure if its the .NET 3/3.5 additions or just slow overall.
I will be doing some app conversions over the next week, and I can do some timings compared to VS2005.