This document contains late-breaking information about Enterprise Library 3.1 – May 2007 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 the Enterprise Library Community site and on the team blogs.
The following sections contain information about this release.
In order to use the included Guidance Packages and the Visual Studio Configuration Editor, you should install Visual Studio 2005 Service Pack 1. If you are using Windows Vista, you should also install Visual Studio 2005 Service Pack 1 Update for Windows Vista. These updates address issues in Visual Studio 2005 that can impact the reliability of Enterprise Library features.
Encrypting configuration using the RsaProtectedConfigurationProvider may fail under Windows Vista. If you use the configuration tool to specify that a configuration section should be encrypted using the RsaProtectedConfigurationProvider on a computer running on Windows Vista, you may receive an error such as “An error occurred executing the configuration section handler for connectionStrings.Failed to encrypt the section 'connectionStrings' using provider 'RsaProtectedConfigurationProvider'. Error message from the provider: Object already exists.” This error is returned from the .NET configuration system, and not from Enterprise Library code. At the time of writing, the cause and resolution are not known, however the issue has not been seen to occur when using the DataProtectionConfigurationProvider.
Performance may suffer when executing large numbers of queries using the SqlCeDatabase. When processing more than 150 queries in a batch, the SqlCeDatabase provider of the Data Access Application Block shows a significant response lag. To workaround this issue you can process the batch of queries by wrapping the batch in a transaction, creating a SqlCeTransaction instance, and passing this instance into each query in the batch.
Some QuickStart Solutions cannot be opened from Windows Explorer. For some of the QuickStart sample applications, double-clicking the .sln files from Windows Explorer will not result in the solutions being opened in Visual Studio as expected. This is a problem caused by the use of non-standard file encoding in the solution files. To open this QuickStart applications, you should open Visual Studio and open the .sln files from the Open Project/Solution command.
Strong Naming Guidance Package may return errors during the first run. When running the “Strong-name all projects in this solution or solution folder” command and selecting the “Update InternalsVisibleTo” option, the operation may fail with an error “Value does not fall within expected range”. This error is intermittently raised by Visual Studio and returned to the guidance package. Running the same command a second time appears to resolve the issue.