This project is read-only.

Enterprise Library 3.0 Release Plan

This plan is subject to change as the development progresses, however we will do our best to keep this up-to-date.
  • December 2006 CTP
    • Released: December 23rd, 2006
    • Highlights:
      • Application Block Software Factory
      • Validation Application Block (partial implementation)
      • Visual Studio-integrated coonfiguration tool
      • AppSettings in configuration tool
      • Data Access Application Block: SQL Compact Edition support
      • Strong Naming Guidance Package
  • January 2007 CTP
    • Released: January 19th, 2007
    • Highlights:
      • Near-complete Validation Application Block (including configuration tool support and ASP.NET integration)
      • Application Block Software Factory, including VB support
      • Data Access Application Block: Improved transaction support
      • Logging Application Block: WCF integration
      • Logging Application Block: Rolling Flat File Trace Listener
      • Visual Studio-integrated configuration tool, with support for multiple sets of EntLib assemblies
  • February 2007 CTP
    • Released: February 28th, 2007
    • Highlights:
      • Preview of Policy Injection Application Block
      • Release Candidate release of all other blocks and features
      • Integrated documentation
      • Environmental Overrides in configuration tool
  • Final Release: Early April 2007
    • Planned Highlights:
      • All done, including Policy Injection Application Block

Last edited Mar 23, 2007 at 7:14 PM by tomhollander, version 3


tomhollander Mar 31, 2007 at 12:41 AM 

Nicolas Mar 28, 2007 at 12:08 PM 
Do you still expect to be able to make a Final release in early April?

jayrt Mar 1, 2007 at 10:24 PM 
We have multiple ASP.NET applications in .NET 2.0. We are trying to come up with standard way to use encryption and also encrypt sensitve data in web.config files. My preference is to use Enterprise Library 2.0 or 3.0 -Cryptography App Block. Someone in the team is suggesting to use DPAPI directly. I am not very clear which one is better and what we get more from using Enterprise Library block. It would really help if someone can tell me what are advantages of going with EntLib vs DPAPI. Thanks

tomhollander Feb 26, 2007 at 11:24 PM 
jayrt: There shouldn't be any breaking changes between EntLib 2.0 and 3.0, so it should be possible to recompile CAB and SCSF against EntLib 3.0. I say "should" as we haven't tested this yet, but we plan to provide guidance on this by the time EntLib 3.0 is released.
Most of EntLib 3.0 will work fine on .NET 2.0. The main exception is around the WCF adapters for Exception Handling and Validation, but this logic is isolated into separate assemblies.


jayrt Feb 26, 2007 at 10:29 PM 
We are using Ent Lib 2.0, CAB and Smart Client Factory [2006 release]. If I upgrade to Ent Lib 3.0, can I still use older (2006) CAB and Smart Client Factory release. Do I have to carry both Ent Lib 2.0 and 3.0 both?

Also I am assuming that I can use Ent Lib 3.0 [Validation Block] with .NET 2.0 ? Is .NET 3.0 is must for Ent Lib 3.0?


GerardoVilleda Feb 19, 2007 at 5:35 PM 
I am new to the Enterprise Library so bear with me. Will the Enterprise Library include a Data Access Application Block that uses LINQ? Or alternatively a transition/integration-path.

rowboater Feb 6, 2007 at 9:01 PM 
Out of curiosity, what happens next? Is this the building blocks for the Web Software Factory? Or will you being going on to expand and maintain this further?

tomhollander Jan 16, 2007 at 8:04 PM 
Just seeing if anyone was paying attention :-). We'll give details on this very soon.

clrudolphi Jan 12, 2007 at 2:12 PM 
Perhaps I missed it, but what is the "Object Policy Application Block"?