Enterprise Library

 

Retired Content
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
The latest Enterprise Library information can be found at the Enterprise Library site.

About the June 2005 Release

Enterprise Library for .NET Framework 1.1

patterns & practices Developer Center

Microsoft Corporation

June 2005

Summary

The June 2005 release of Enterprise Library is a minor update of the original January 2005 release. This release contains the same seven Microsoft patterns & practices application blocks, and it incorporates the patches and extensions previously released to the Enterprise Library Community site. In addition, it includes several minor fixes and improvements.

If you are using the January 2005 release of Enterprise Library, and you are worried about the impact of upgrading to this new version, you should not consider this a mandatory 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 upgrading to the new release. However, for new development, you should use the June 2005 release.

The sections below highlight the most significant changes.

Contents

Across Blocks
Configuration Console
Configuration Application Block
Caching Application Block
Logging and Instrumentation Application Block
Data Access Application Block

Across Blocks

The updates to the Enterprise Library that affect all of the application blocks are the following:

• A memory leak was fixed in the January 2005 version of the Configuration Application Block that affected all of the application blocks. This fix was made available in Patch 1475 and is included in the June 2005 release.
• The Configuration Application Block was modified to improve performance when reading configuration information. Because each application block uses the Configuration Application Block to obtain configuration information, any application that uses an Enterprise Library application block will benefit from these performance improvements when moved to the June 2005 release.
• The application blocks were modified to always retrieve string resources using CultureInfo.CurrentUICulture. This represents the current culture used by the Resource Manager to look up culture-specific resources at run time.
• The version number for all of the assemblies was updated. This will allow side-by-side installation of the January 2005 (version number 1.0) and June 2005 (1.1) versions of the Enterprise Library package.

Note   The January and June versions can both be installed and used on the same computer. However, the assemblies that comprise the releases are not intended to be used interchangeably. For example, you cannot use the January 2005 version of the Data Access Application Block with the June 2005 Configuration Application Block.

Configuration Console

The updates that affect the Configuration Console are the following:

• You can now add multiple distribution strategies to the Client Settings of the Logging and Instrumentation Application Block. In the previous release, the Configuration Console did not allow you to add either an In Process or MSMQ distribution strategy if the configuration already contained a distribution strategy.
• You can now change the location of the saved configuration file.
• You can now reorder Oracle packages using the Configuration Console.

Configuration Application Block

The main updates to the Configuration Application Block incorporate fixes and improvements included with Patches 1475 and 1473 for the January 2005 release of Enterprise Library. Patch 1475 was discussed in the "Across Blocks" section. Patch 1473 addressed configuration extensibility and included additional storage providers. The new storage providers included with the June release are:

• Application Configuration File Storage Provider. Allows you to read and write data to an application domain configuration file (for example, the App.config file).
• Registry Storage Provider. Allows you to read and write data to the registry.
• SQL Storage Provider. Allows you to read and write data to and from a SQL database.

Note   The source files for the new storage providers are located in the Storage folder within the Configuration project.

Caching Application Block

The main update that affects the Caching Application Block is the fix that allows the application block to be used without the instrumentation compilation directives.

Logging and Instrumentation Application Block

The updates that affect the Logging and Instrumentation Application Block are the following:

• Whenever a relative path is specified, the FlatFileSink class writes files to the location relative to the AppDomain.CurrentDomain.BaseDirectory path. If an absolute path is specified, the system logs the file to the absolute path.
• The flat file sink was changed to be thread safe. A multithreaded application can use the flat file sink without risk of data loss.
• The Logging and Instrumentation Application Block no longer fires the LoggingLogWrittenEvent and LoggingLogDistributedEvent WMI events for the InProc strategy. This reduces the number of times a message must be formatted, resulting in improved performance. Applications that require messages to be logged using WMI can be configured to use the WMI sink.

Data Access Application Block

The updates that affect the Data Access Application Block are the following:

• The new method named GetStoredProcCommandWrapperWithSourceColumns is added to the Database class. This method provides creation of a stored procedure command wrapper whose parameter values come from source columns in a DataTable. In addition, new public methods provide access to the DbDataAdapter object for the current database connection.
• The DataConnectionFailedEvent and DataConnectionOpenedEvent classes are updated to be thread safe.
• The OracleCommandWrapper class is updated to perform proper conversion between parameters of types not recognized by Oracle and native Oracle types.

Start | Previous | Next

Retired Content
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
The latest Enterprise Library information can be found at the Enterprise Library site.