Monday I collected the current survey results from the people that have been using the MSBee CTP. I wanted to share what we heard with all of you.
We received a total of 21 responses for 75 survey requests that were sent out. It feels like we mostly hit C# component vendors that were building class libraries that reference other .NET 1.1 DLLs. The MSBuild team blog was the best marketing we had for the first CTP and ¾ of the people who wanted Asp.Net project support would be willing to use the Asp.NET project template that was released as an aftermarket solution.
This survey mostly validates the direction we are taking, but the biggest pain point for customers seems to be that lack of easy IDE integration and having to manually edit the project files.
Actions from This Data
How did you hear about the MSBEE CTP?
The MSBuild specific audience blog was our most effective communication tool about the first CTP. We posted in the forums as well. It will be interesting to see if this changes after we post to its own download site for the public release.
What languages have you used the MSBEE tool with?
C# developers formed the majority of our early adopters. We should specifically make sure we are hitting the right ration here in the second CTP to have more confidence in VB projects. Perhaps a specific mail to the VB MVPs in the second release.
Tools/Tasks Used Frequently During Build
The AL and Strongname tool were most commonly used.
Important Feature Ranking
Ranked low to high by adding 1 point for 1st, 2 points for second, etc. Less points = ranked higher.
Yes/No – Willing to use the Asp.NET Web Project Template Solution?
16 of 21 people said they would be willing to use the Asp.Net project file model.
Project Types Used
Most people were building class libraries and there was a high degree of overlap between the class libraries and windows forms projects.
Verbatims – Other Comments/Suggestions
There are a couple of more feature suggestions and bugs that I left off of this blog posting because the give away some information about the solution the user was developing.