Feature Prioritization for Enterprise Library v3

I'm sure all you regular viewers have noticed that we've been doing a lot of probing to find out how people are using Enterprise Library today, and figure out where we should invest our efforts in our next release. First I posted a blog entry asking for any and all crazy suggestions on what the new release should include. This resulted 142 comments - some of them more crazy than others - but we did comb through them all in an attempt to locate the hotspots.

Next we launched the Enterprise Library v2 Exit Poll, which is a web survey for people who have recently completed projects using Enterprise Library. This survey is still running and we have not yet analyzed the data in detail, but we are starting to get a good picture on what you are saying works well and which areas are candidates for improvement.

While we've learned a lot from the verbatim comments from both of these exercises, so far it hasn't been possible for us to get a good understanding of the relative priorities of the various features we are considering. For example, if 2 people posted comments to the first blog entry saying they want feature X, we can't tell if those are the only 2 people in the world who want that feature, or if everybody and their dog wants it (but didn't feel compelled to post since it had already been said).

So in what will hopefully be the last survey I'll bombard you with for the time being, we are asking for your help one more time in prioritizing some of the candidate features for the next release. The list should hopefully look familiar as we mined the suggestions from the blog and exit poll survey results - but if we missed anything important there is room for you to add some suggestions of your own. The survey allows you to vote for up to 20 features in priority order, but feel free to stop before you get to 20.

Here's the link to the survey. As always, thanks for your help!

Comments (6)
  1. El Bruno says:

    Feature prioritization for EntLib v3 Feature prioritization for EntLib v3 (8/29/2006 12:15:49 PM) As

  2. Thanks Tom,

    I noticed all of my survey suggestions made it on the list!  Thanks so much, you guys are really giving me a lot of hope (especially with the ODP.NET stuff).


  3. Rich says:

    I love the idea that you guys are taking our input and using it. Thanks for taking the time to listen to the developers.

    Just a suggestion, but that was an awful format for a survey… I think we can all agree a quick ASP.net app with a SQL data source could have run circles around that one…

    But oh well, just my two cents. I understand the bandwidth/cost issues and all that…

    Gotta find something to complain about!

  4. Vagif Abilov says:

    Hi Tom,

    I was late to throw my suggestions regarding changes, but there is one that cost almost nothing to implement. Right now EL Logging Block creates a new file if the flat file is locked. It generates a GUID and names a new file using this GUID and the original name. This makes it impossible to sort log files in case logs for different event listeners are stored in the same folder. Could you consider swapping GUID with filename, i.e. that the new file would constist of the original filename and a GUID appended as a suffix, not prefix? This will make log file folders to look so much better!



  5. El Bruno says:

    Feature prioritization for EntLib v3 Feature prioritization for EntLib v3 (8/29/2006 12:15:49 PM) As

Comments are closed.

Skip to main content