We had a fantastic response to the Enterprise Library for .NET Framework 3.0 feature prioritization survey, with over 300 people sharing their ideas. I wanted to share the results, as we found them to be pretty interesting.
But first, it’s important for everyone to understand that while customer feedback such as this is the most important factor in determining what we build, it’s not the only factor. We also need to consider things like project resources, the skills we have on our team, alignment with current and future Microsoft products and p&p guidance, and so on. At this stage we haven’t been able to consider all of these factors, so we can’t say exactly what will actually make it into the new release of Enterprise Library – but it is safe to say that it will be heavily inflenced by the results of this survey.
And now, the results:
The first graph shows the number of points allocated to each feature in the survey. We used a simple algorithm giving 20 points for a Priority 1 vote, 19 for a Priority 2 vote, down to 1 point for a Priority 20 vote. (If there are any statisticians in the audience who would like to suggest a different approach for analyzing the results, let me know :-). Here’s what you told us:
Here is the legend to help you decipher this chart:
Caching Application Block
Cryptography Application Block
Data Access Application Block
Exception Handling Application Block
Logging Application Block
Security Application Block
Docs and Samples
I also did another graph that shows the totals for each feature area by combining all of votes for each individual feature. This graph isn’t quite as useful for prioritization as it’s highly unlikely we’ll get to everything on the list – but it does show which feature areas people are most interested in:
I hope you found this interesting – as we get a more detailed picture on what will actually make the cut, we’ll keep you in the loop.