Tom Hollander's blog

Head in the clouds

Enterprise Library for .NET Framework 3.0 - what would you like to see?

Enterprise Library for .NET Framework 3.0 - what would you like to see?

We're getting ready to start the planning process for the next release of Enterprise Library which will target .NET Framework 3.0. In case you missed it, .NET Framework 3.0 is the new name for what used to be known as .NET Framework 2.0 combined with the new WinFX class libraries for WCF, WPF and WF. For more information on the name and version, check out Soma's post.

While we expect that the new WinFX libraries in .NET 3.0 will require us to make certain updates or changes to existing blocks (for example, to allow the Logging Application Block to work within a WCF pipeline), the platform change isn't going to be anywhere near as significant as the move from .NET 1.1 to .NET 2.0. This is hopefully good news for you, as it means we can focus more of our energy on improving the library in other ways.

So where should we focus our efforts? While we have a few ideas up our sleeves, the best ideas are likely to come from people who are using Enterprise Library on real applications (and if you're still reading, that probably includes you!). So don't be shy - tell us what you want!

Instead of just providing a feature list, imagine you have $100 (Australian dollars, of course) to invest in the our new release. If there's only one feature you care about, you can invest all $100 in that feature. If you want 5 new features or changes, you could invest $20 in each of those, or you could split it up differently depending on how important each request is to you (eg $60/$20/$10/$5/$5).

Please use your imagation and come up with whatever crazy suggestions you want for this new release. But to help get you started, here are a few feature areas you may want to consider:

  • New blocks (please specify what these blocks should do)
  • New providers for existing blocks (please specify which blocks and what the providers should do)
  • Integration with new WinFX features (which ones?)
  • Changes to the internal architecture (what and why?)
  • Better support for deployment or operations processes
  • Performance improvements
  • Improvements to the configuration tool (such as?)
  • Improvements to the documentation (such as?)
  • New or improved samples or training materials
  • Software factories or guidance packages to help you build blocks or providers
  • VB version of the block source
  • ...anything else?

Please limit your suggestions and your virtual investment to things that belong in Enterprise Library. The p&p team is continuing to work on a bunch of other projects such as our new Software Factories for scenarios such as web services, smart client and web development - but these are all different projects to Enterprise Library (even though many of these will leverage EntLib blocks). Enterprise Library is - and will remain - a library of general purpose application blocks for common development scenarios.

  • Yes you heard right.  There will be a new version fo Enterprise Library coming out. Version 3.0,...
  • Hi Tom,

    Exception handling policy that goes with the WCF FaultExceptions. I have already implemented it, but I think it should come out of the box.

    Better documentation + Hands on Labs that will ship with the release of the Entlib and not 4 month after.

    Good Luck, Guy
  • 1) CAB/SCSF for the Mobile platform:
    ObjectBuilder's run-time lookups (reflection) may be too expensive for Mobile computing. Another run at it, perhaps, with 3.0?

    2) More guidance as GAT recipies. You pick.

    3) A best practice for deploying a Client/Server solution to a customer that supports two levels of ClickOnce®. One from me to customer's server, another from their server to their clients.

    Thanks Tom.
  • Don't let the title confuse you. There is no new version for Enterprise library for .Net Framework 3.0....
  • John - check out the Mobile Client Software Factory at

  • I would invest:
    - $80 in ORM and LINQ Support
    - $20 in deep integration of the configuration tool with the Visual Studio IDE

    Hope this helps,
  • The Enterprise library team are planning for a new version which will target .Net Framework 3.0. Tom...
  • Hi Tom (and the team)

    Thanks for asking.

    I would like to see more use of the Object Builder. I really like the mechanism, but it couldn't do what I wanted. Therefore I created a Service Application Block of my own to put under configuration.

    I would like to see such a service application block as part of EL 3.0.

    The basic idea is:

    - Everything with an interface is a "service"
    - ObjectBuilder can create concrete instances of the interface
    - Mapping between interface and concrete class is placed in configuration
    - Configuration includes other stuff, too. Should I create this as a singleton or new instance everytime, etc.

    That way you can do an OB instance creation like this:


    I use it for a layered server side application (WCF), where I have the follwing layer (top down):
    - WCF
    - Coarse-grained business
    - Fine-grained business
    - Persistence

    All calls from layer to layer goes through an interface. ObjectBuilder takes care of instantiating and preparing the concrete instance... It even lets me change what concrete instance through configuration.

    This is only the basic idea. Maybe you and the team have some more stuff to put in.


  • Do Something For transaction handling.
    In 2.0 we have to pass transaction to each record which we uses.
    I didn't think so that it is a good practice to pass transaction to every method.
  • Este tipo de noticia es de las que me gustan ...
    A proponer mejoras !!!&#160;

    Enterprise Library for .NET Framework 3.0 - what would you like to see?

    Enterprise Library for .NET Framewo ...
  • $20 - Easy way to upgrade existing applications
    $60 - WinFX & WinCF, LINQ (if not, why it is El for .NET 3.0?)
    $20 - Integration with VS (DSL, WorkFlow)
  • 1. Much Improved (auto)Setup - I can't speak for those who have been using the library and have become very familiar with it. As a newcomer, the library seems to be an an example of poor design... before you slap me, how is it that the library is not configured so that it requires virtually no setup? Where is the "Test Connection" Dialog? Why do I have to find and locate installer .exe files? Who belives that a console window popping up to show that "stuff" is loading is a good thing.

    2. Trimmed QuickStarts - the "quickstarts" simply are not. My lord, when logging messages requires one to scratch their head to try and figure out how to create one, there is a serious problem. I think someone keeps forgetting that the primary goal of an application is managing end-user actions, provide intuitive feedback, and mimimizing the effort to achieve that.

    Personally, it looks like someone lost the focus of developing the IL in the first place. What a great concept: program in VB, C#, C++ - whatever and it gets compiled into a uniform IL. Instead, the kids just can't leave the concept of  "new" toys and muck the whole darn thing up with HTML,XML, XAML, Java, blah, blah, blah.

    To me, it'll be "right" when I don't have to design in multiple languages and instead, the language I use does it for me. Furthermore, if you can't provide a "self-installing" example that doesn't require manual configuration - its a rotten example.

    Not trying to offend - just be blunt.


    How about that?
  • This should only cost 20AUD:

    Please include support for Event Tracing for Windows (ETW). There's about five different frameworks in .NET that support it already. I understand that Orcas timeframe .NET will include an official API, however I would really like to see EntLib 3.0 include custom P/Invoke support for ETW. I feel that the high speed event tracing service in ETW is an essential part of having a truely supportable event logging architecture. I have previously built architectures around the <a url="">Paul Bunyan</a> by Diamond Sierra, which includes a high speed logging service.

    There should be no reason to go with a third party product since ETW is available in Windows XP and Windows 2003 (and Windows 2000, for that matter). However, I have found no .NET wrapper for the ETW apis.
  • Hi Tom,

    An aspect-orientation block, similar to the one from Avanades ACA.NET extensions to Enterprise Library, would be a powerful addition to the existing blocks.

    For those that haven't seen the aspect-oriented features of ACA.NET before, there is an example at the end of the following article:

    Examples of possible aspects include: instrumentation, auditing, caching, exception handling.

    At first glance, Avanades offering seems tightly bound to their approach to service orientation thats now superceeded by WCF, so a solution aligned with WCF would seem useful.

    On another note, is it possible for Enterprise Library to evolve from a guidance initiative into an officially supported product?

  • Hey all, did you know that Tom Hollander is looking for great ideas to enhance the quality and functionality...
Page 4 of 10 (145 items) «23456»