I like getting WPF feedback from the community. I talk to customers, look at blogs, scan forums, and have standing searches set up on Twitter. The feedback I get is great, but it's not structured or contained in all one location.
We’re now in the early planning stages for WPF v.next. Following some of the great work folks like Tim Heuer have done in making the Silverlight planning process more transparent and open since our last WPF release, the WPF product team has created the WPF public feature request and voting site at uservoice.
How it Works
I’ve seeded the list with common feature requests I’ve heard, as well as read on various WPF-enthusiast blogs out on the tubes. If you see something you want, vote it up. If you don’t see something, add it as a new feature suggestion.
Each user gets 10 votes to spread across the features that matter most to them. The features with the most votes are the ones that the community feels are the most important.
If you run out of votes, you can change your existing votes. You’ll also get votes returned to you when we mark an idea as completed or on the rare occasion when an idea is deleted.
When adding new suggestions, help us out by describing the scenario in which you’d use the feature. The better the description and title, the more likely it will get voted up by the community.
Of course, this isn’t the only way we get customer feedback into the products. MVPs, Influentials, major customers and ISVs, internal users (think: Visual Studio and Expression teams and others) and others all have an impact on what features make it into the final product. The combination of all these feedback channels helps us create the best possible product with the right feature set.
So go and visit our new feature voting site, tell your friends and colleagues about it, and vote for the suggestions and features you want most in the next version of WPF. I’m looking forward to seeing what the community really wants in the next version of WPF.