Microsoft Enterprise Library 5.0 Beta 1 – February 2010 Release Notes
This document contains late-breaking information about Microsoft Enterprise Library 5.0 Beta 1 –February 2010 that could not be included in the documentation. Any additional information and bug fixes that are delivered after the release date will be available
on this site.
The detailed change log is included in the HTML Help documentation (.chm file) installed with Enterprise Library and also
This is a preliminary release of the code and documentation that may potentially be incomplete, and may change prior to the final release of Enterprise Library 5.0.
This release does not include the final test pass, full platform testing, and integration testing with Microsoft Visual Studio that will be completed for the final release. We do not advise use of this Beta release in production applications. It is provided
for preview and evaluation purposes only.
This release should not be interpreted as a commitment on the part of Microsoft as to any new features or improvements, and Microsoft cannot guarantee the accuracy of any information that may indicate features or changes to future releases.
Your Feedback is Invited
Organizations are encouraged to begin their Enterprise Library 5.0 and Unity 2.0 evaluation now. This release is intended to be a feature complete version of Enterprise library 5.0, with the exception of the Visual Studio integrated configuration tool.
We would appreciate feedback on any issues found, or any other general comments on this release. You can post feedback and comments on the
Enterprise Library Codeplex forum
. Please prefix subjects of your comments with "BETA1". When filing an issue in the
, please make sure to associate it with this Beta1 release.
The following are the known issues and important information about this release:
Manageability Configuration Source
- The configuration tool does not save the Manageability Providers settings in the configuration file.
- The configuration tool does not support configuration settings in a parent configuration file or a redirected file.
- If you have existing Group Policy Administration (ADM) templates for the Logging Application Block or the Exception Handling Application Block, you must update these using the new configuration tool.
- When persisting a file based configuration source to the same file that's being edited in the Enterprise Library configuration tool, the enterpriseLibrary.ConfigurationSource section does not get persisted.
- Configuration source in the configuration tool can only point to an existing well-formed XML file.
Data Application Block
- Sharing connections when an ambient transaction is present causes failures when invoking an operation if a
DataReader obtained with the ExecuteReader method is active.
- The input.Arguments collection available within a behavior when using interception has incorrect values for ref and out parameters, and does not correctly reflect the parameter direction.
- The Interface Interceptor will intercept the call twice when the intercepted interface or class contains an attribute.
- Behaviors that have the willExecute property set to false are not skipped, and will still execute.
- Method access exceptions occur when building up List<T> on the .NET Framework version 4.0.
- Interception fails when using a Transparent Proxy Interceptor and calling a generic method on an interface.
- Dependency injection does not occur for explicitly implemented properties.
- The Not Null Validator only works correctly when used in combination with one or more other validators. When used alone, validation does not occur.
- Object collection validation does not occur for recursive collections.
- The value of the MessageTemplateResourceType property of a validator is ignored.
- The façade driven approach for using the Policy Injection Application Block (the default approach in versions 3.x and 4.0 of Enterprise Library) incurs a considerable performance overhead in this release compared to previous versions.
- The methods of the SQLCeDatabase class do not take advantage of pooled connections.
Logging Application Block
Policy Injection Application Block
- Malformed messages can cause the distributor service to shut down.
- The user name and password settings for the Email Trace Listener are displayed as clear text in the Enterprise Library Configuration tool.
Caching Application Block
- The Caching Call Handler uses the GetHashCode method to compute the cache key. This means that there is a possibility of key collisions and subsequent data disclosure in multi-user scenarios.
- The Caching Call Handler uses the ASP.NET System.Web.HttpRuntime.Cache class to perform caching. This may result in memory leaks because the ASP.NET Cache class is not designed for use as a caching mechanism in non ASP.NET applications.
- You must ensure that partition names are unique for each application if you use the same shared database as the backing store for more than one application. If not, key collisions may occur between applications resulting in data disclosure.
- The SourceChanged event continues to be raised for sections that have been removed from the configuration.
- When a section in redirected configuration file is updated, two notifications are raised for the same section.
- Not all of the Matches settings for Matching Rules in the Policy Injection Application Block Settings section are retrieved when configuration is merged.
- The new Enterprise Library configuration tool is still "work in progress". It has undergone considerable testing, but there are some outstanding issues. Please report any that you encounter.
- If you configure multiple environments in the configuration tool, adding configuration sections (such as application block sections) is noticeably slower.
- In the new Unity configuration tool, deserializing from old Unity configuration files may fail. Workaround: update the old configuration files to the new Unity 2.0 schema to use Unity configuration tool.
- The signature for the FileConfigurationSource.Save method has changed.
- Some of the Enterprise Library unit tests use features of the Moq mock object library. We cannot include these libraries as part of the Enterprise Library 5.0 download. To run the unit tests, please download the binaries for Moq 3.1 (current version as
of this writing is 3.1.416.3) and unpack the binaries and place them in this directory. Both the desktop and Silverlight binaries can be placed here. You will then be able to compile and run the unit tests.
- No quickstarts are supplied with this beta release. They will be available in the final release.