Tom holanderI published an article a few days ago.Post, Puts forward someEnterprise Library v3(For the next versionEnterprise LibraryThe specific name is not specified. Use it nowEnterprise Library v3As the development code) before the preliminary development plan, he once releasedEnterprise Library 3.0Collection of development opinionsAccording to user feedbackEnterprise Library v3Preliminary (non-final) Development Plan:
LMedium trust support
LManageability extensions for configuration (WMI, Group Policy)
LSimple strong-naming
LMini-factory for building your own blocks and providers
LValidation Application Block
LException Handling: WCF integration (exception shielding/fault mapping)
LLogging: WCF pipeline Integration
LAuthz: WCF pipeline Integration
After the above list is completed, the following will be implemented:
LConfig tool: embedded in the Visual Studio ide
LDaab: SQL everywhere support
LDaab: richer transactions support
LDocs: More code samples
LDocs: detailed documentation for objectbuilder
LDaab: Batch support
LConfig tool: edit your ettings and other. net settings
LConfig tool: Environmental overrides
LConfig tool: encryption support
LConfig tool: Improved Type Loading behavior when assemblies can't be found
LLogging: Rolling flat file tracelistener
LLogging: local or UTC timestamps in formatted log messages
LLogging: reflected property tokens
LAbility to create custom production instils
LAbility to create custom developer instils
LException Handling: localization of exception messages
LDaab: ODP. net provider support
This plan is also a preliminary development plan, which has not yet been finalized.
For details, visit:Http://blogs.msdn.com/tomholl/archive/2006/09/26/773213.aspx