Are we expecting any more updates to this toolkit or this project is abandoned?

Can this be updated with respect to WPF in VSTS 2010? It's a long time since February....

What is the purpose of virtualization for controls like combobox and datagrid? Does it allow more data to be added/displayed to control without bogging down memory? I created a small app with the new WPF Toolkit Datagrid and it seemed to take a long time to add to the datagrid. I debugged the code and it does not seem to take that long to read data from database. It returns about 3600 records with 10 fields. When I set the datagrid's itemsource to results, it seems to lock the app for a few minutes before displaying data. Is this where the virtualization should work? Does the datagrid include this feature? Thanks in advance.

y2k4life - If you check out the roadmap for the Futures and Toolkit, things might be a little more clear. The reason the releases are broken down like this is to keep clear separation between the intentions of the different controls.

The Futures bucket is mainly for samples and getting a feeling from the community about whether or not customers and partners feel the controls in the Futures are worth investing more time in. Unless we get a lot of feedback asking for these features to be developed more (and moved to the Toolkit and/or Platform), then they will stay in the Futures release as samples.

The Toolkit will have more full-featured controls with a higher quality bar. Some of these controls will have started out in the Futures, whereas others were put immediately into the Toolkit release. Some (but not all) of the Toolkit features will eventually be moved back into the platform. In the case of something like DataGrid, this is a control which we definitely want to be in the Framework, but we decided to release it in the Toolkit in order to get it out to the community quicker, before our next platform release happens. We didn't put it in the Futures because we already knew that there was a lot of demand for a DataGrid in the community, so we were able to skip that step. There are other features, however, which may stay in the Toolkit. These decisions will be made based on feedback from the community and the team's readiness to make these transitions.

I understand that this could be confusing. If you have any suggestion about how we could make this plan more clear to the community, please let me know what they are! Thank you!

Thanks for your comments DaCodeBoy. As you mentioned, we don't have any information about future plans for WPF posted here yet. We are still in the process of planning for our next release and will add more information about our future plans as they become more firm.

Why are these project so fragmented we have Futures, Toolkit, and Platform. I see this pattern with other projects as well like ASP.NET. Then you try to read a Roadmap and you can't tell if the Toolkit will become the Platform, or if the Futures will. Let alone if the next Platform release will have parts of the toolkit or parts of the Futures or will it have a little bit of this and little bit of that. Then to figure out if this will be in the next .NET release or servier pack or a seperate add on to the .net framework. How do the project managers sleep at night with so many sub projects within a project and figuring out what gets released next.

This isn't a roadmap; it's more like release notes. Any notes on what to *expect* in WPF?