Tom Hollander's blog

patterns, practices and pontification

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.

  • Tom,
        I would love the ability to have different logging providers that are active only at certain log-levels.  For instance, I want all high-priority messages for a given category to go to one provider, and lower ones to go to a text file.

    Andrew
  • I would like to see:
    1) 80$ for good designer probably made using Visual Studio DSL technology. This designer should allow me to develop in both UI block for PC and mobile: UseCases, Flow control, etc
    2) 20$ for support new WPF and WPF/E

    And many more, but I will write it ASAP :)

  • I would like to see the data access block be able to perform smart updates inside a transaction for a data set that contains multiple tables.  Deletes should be performed from bottom up, inserts/updates from top down.  You should be able to use the relationships in the data set to derive the order in which to perform these.  The block should include a transaction to do a rollback.  You should also include support for a timestamp column to use for optimistic concurrency tests.
  • 1. A really serious focus on key scenarios & examples for ASP.NET. No more HOL's that claim to demonstrate ASP.NET through Winforms.
    2. A security rules engine that utilizes CODEDOM
    3. A provider that stores configuration info in SQL
    4. A Web version of the Configuration Console
    5. A Single demonstration project that employs all the key scenarios listed for each block
    6. Completely self contained unit tests or at least better documentation on the setup and dependencies to run the tests.
    7. An XML manipulation block. The base .NET library has great support but there are many simple operations which require too much code.
  • $100 for some decent documentation or usable version of ObjectBuilder.  If I want to use EnterpriseLibrary, it would sure be nice to not to have to go looking for an IOC container as well.
  • I would like to see:

    1) 80$ for Improve Software Factories, this will be a great programming help, automatization is a great need, specially in SOA Application with WCF, and link closer with App Block.

    2) 20$ for Improve Documentation.

    Thanks
  • I would like to see a block committed to combining results from 2 webservices (xml docs) into one document -- a true data aggregator block.  I'll spend $95 of my AUS bucks on that and keep the other $5 for food and alcohol. No way I'm spending $100 on my stupid computer.
  • How about support for ODP.NET in the Data Access Block?
  • Kevin - we Aussies take for granted that for every $100 you spend on tech stuff, you'll be spending $500 on beer.
  • I aggree with Kevin White for:

    7) An XML manipulation block. The base .NET library has great support but there are many simple operations which require too much code
  • I would like to see some effort to be spent on UIP block. As with 2.0, lot of things have changed like master pages, site maps etc. We need to get UIP block upto speed on that.

    Also in view of the WPF, it might be interesting to see if we can leverage the benifits in the same block.
  • I agree with some sort of update around UIP although it should still be separate from Ent Lib.
  • I'm with Larry: support for Oracle's .NET providers (ODP.NET) in the Data Access Block is definitely needed.

    Also sort out ObjectBuilder so it can do IOC properly.

    I'd split the budget 70/30 on these two.
  • I would spend $100 USD on a new version of the User Interface Process (UIP) block -- it's definitely long overdue.  Amongst the new features should be support for web user controls (as views.)
  • Well I would like to see more on Documentation - Complex Examples - Hands On Labs, but everything on the same day the new fremework is available (70$)
    A provider for the logging block(?) that publishes objects-counters on the performance monitor. May be available through diferent log levels (20$)
    I agree with the configuration web console(10$)
Page 1 of 10 (145 items) 12345»