Enterprise Library June 2005 (the '1.1 release')
Yesterday a customer pointed out to me that we haven't made a lot of information available about the upcoming June 2005 ("1.1") release of Enterprise Library (sorry, Gil!). While this wasn't at all deliberate, it is a fair observation - it's been mentioned in passing in some of the gotdotnet message boards, but we haven't provided a clear description of the purpose, scope or implications of this release in one place. So I'll try to do this now.
The June release was really born out of the memory leak that was discovered in the January release, and addressed by Patch 1475. We were able to get a patch out very quickly, but we know that the patching process is a little clumsy, and that there is a risk that some users won't apply the patch. So right from the discovery of this issue, the plan was always to roll this fix into a new installer. Since this is almost certainly going to be the last release of Enterprise Library for the .NET Framework 1.1, we also decided to use this opportunity to fix a number of low-to-medium priority bugs that have been discovered after the release.
In a nutshell, the June release will be the same as the January release, with the following changes:
- Patch 1473 (for configuration extensibility) and all of the extension configuration storage providers (but not the MVP Transformer) will be rolled in
- Patch 1475 (for the memory leak) will be rolled in
- A few fixes to the Data Access Application Block to make it work better with Oracle
- A couple of additional methods in the Data Access Application Block that provide access to DataAdapters
- Some performance improvements to the Logging & Instrumentation Application Block
- A fix to the problem with the Caching Application Block when the instrumentation is compiled out
- A few other miscellaneous minor fixes
We will have a more complete list of the changes included in the documentation. Also we will be revving the version number for all of the assemblies, and we will allow side-by-side installation of the January (1.0) and June (1.1) versions of the Enteprise Library package.
If you are using the January release of Enterprise Library, and you are worried about the impact of upgrading to this new version, you should not consider this a necessary upgrade provided you have installed Patch 1475. All of the changes in the June version should help improve the experience of using Enterprise Library, but since most of the fixes only apply to a small number of usage scenarios, you may find that the benefits of the new version do not outweigh the impact of changing to the new release. However, for new development there should be no reason not to move to the June release right away.
This posting is provided "AS IS" with no warranties, and confers no rights.
