Again, some raw quotes and what I think I heard at Tech-Ed. This time about the community tech previews.
Of all the things gathered information on I probably got the least feedback on the topic of the Community Tech Previews for Visual Studio. One item that is not captured in quotes is that it would be MUCH MUCH better if users could use the developer tools to target more stable frameworks. Unfortunately our tools are tied to the framework at the moment. Eclipse was held up as an example of how any build of eclipse could easily be used for real development on existing projects that hit any version of the Java runtime.
The second big pain point was on the issue of distribution. We need a faster, more scalable, solution for users that want to play with our builds more frequently. Most people agreed that they would be willing to support a P2P distribution model, but not a pay-for download model that they perceive the current MSDN subscriber limitation as. The third pain point is the install process. Its too long and old builds don't uninstall.
In general people didn't mind if the builds were very broken IF they were able to identify what worked and didn't work before they went through the lengthy download/install process.
There was laughing when I explained the one week bug report -> using a fixed build scenario, but in a good way I think. I see that as a challenge.