entlib Wiki & Documentation Rss Feed

Updated Wiki: EntLib6ReleaseNotes

dominicbetts — Fri, 17 May 2013 05:05:47 GMT

Microsoft Enterprise Library 6 – Final Release

Release Notes

Updated 4/25/2013

Welcome to the final release of Microsoft Enterprise Library 6!
This document contains a brief summary of Microsoft Enterprise Library 6, including late-breaking information that is not included in the main documentation. Additional information and bug fixes delivered after release are available on the Enterprise Library Community site and on the Enterprise Library MSDN site.

Where to get it?

Via NuGet – use the NuGet Package Manager in Visual Studio and search online for the “enterpriselibrary” packages. Pick the official Microsoft packages.

What’s New in this Release?

This major release of Enterprise Library contains many compelling new features and updates that will make developers more productive. These include:

Major changes throughout Enterprise Library to make it simpler and easier to learn and use whilst minimizing the impact of these changes for existing users.
A new Semantic Logging Application Block to make it easier to adopt semantic/structured logging in your applications.
The addition of the Transient Fault Handling Block as a full member of the library to help you make your on-premises and Windows Azure based applications more resilient to transient errors.
Several enhancements to Unity type registration to help you streamline the registration of types in the Unity container.
Support for Windows Store apps.
Simpler programmatic configuration for all the blocks.
Deeper integration with other technologies such as ASP.NET MVC and WebApi.

The detailed change log is included in the Enterprise Library documentation and also at the end of this document.

Installing with Previous Versions of Enterprise Library

You cannot install Enterprise Library 6 side-by-side with a previous version of the library in the same Visual Studio project.

System requirements

Supported architectures: x86 and x64.
Operating systems: Microsoft Windows® 8, Microsoft Windows® 7, Windows Server 2008 R2, Windows Server 2012.
Supported .NET Frameworks: Microsoft .NET Framework 4.5, .NET for Windows Store Apps (previously known as WinRT) for Unity and the Transient Fault Handling Application Block.
Rich development environment: Microsoft Visual Studio 2012, Professional, Ultimate, or Express editions. The database setup scripts depend on the SQL Server Data Tools that are included in a standard installation of Visual Studio.

For the Data Access Application Block, the following is also required:

A database server running a database that is supported by a .NET Framework 4.5 data provider.

For the Logging Application Block, the following may be required:

If you are using the Message Queuing (MSMQ) Trace Listener to store log messages, you need the Microsoft Message Queuing (MSMQ) components installed.
If you are using the Database Trace Listener to store log messages, you need access to a database server.
If you are using the E-mail Trace Listener to store log messages, you need access to an SMTP server.

For the Semantic Logging Application Block, the following may be required:

If you are using the SQL Database Sink to store log messages, you need access to a SQL Server database server. The following are supported: SQL Server 2008 and higher, SQL Server LocalDB, Windows Azure SQL Database.
If you are using the Windows Azure Sink to store log messages, you need access to a Windows Azure storage account.

For the Transient Fault Handling Application Block, the following is required to install the NuGet package:

NuGet 2.2. This is included in Visual Studio 2012 Update 2. Once the package is downloaded, you can copy the assemblies to a machine that does not have NuGet 2.2 and use the block there.

If these dependencies are not met, you may not be able to use certain Enterprise Library features.

Learning More

The following learning resources are recommended:

Enterprise Library Reference Documentation
Unity Reference Documentation
Enterprise Library Developer’s Guide
Unity Developer’s Guide
Migration Guide
Hands-on Labs (available later)
Discussion forum

Providing feedback

Microsoft would appreciate feedback on any issues found, or any other general comments on this release.
To report a bug, use online Issue Tracker. Other feedback or questions can be posted on the Enterprise Library Codeplex forum.
We look forward to your comments!

Support

Community support is provided via Enterprise Library Codeplex forum.

Known Issues

If you are using the Transient Fault Handling Application Block, you should ensure that you are using version 4.0.30319.18003 or later of mscorlib.dll, otherwise you may see a VerificationException exception at run time. For more information, see http://support.microsoft.com/kb/2748646.
If you are using the Transient Fault Handling Application Block, you must have NuGet 2.2 in order to install the NuGet package. Note that this update is included in Visual Studio 2012, Update 2.
To run the coded UI tests in the Reference Implementation solutions, you must have the Visual Studio 2012 Ultimate edition.
The Semantic Logging Application Block uses the TraceEvent library (http://bcl.codeplex.com/wikipage?title=TraceEvent) internally. The Globalization Warnings reported by FxCop static analysis in this library have not been addressed.
The Semantic Logging Application Block running out-of-process only supports logging events authored using the managed EventSource class.
Using the Semantic Logging Application Block, you should not new up a listener, write a log message, and the dispose the listener. The typical usage pattern is to initialize listeners during application start up, log messages while the application is running, and then dispose the listeners during application shutdown.
When you author a custom EventSource to use with the Semantic Logging Application Block, you should only use enum types of int32 or int64. For more information, see http://connect.microsoft.com/VisualStudio/feedback/details/785409/eventsource-manifest-generation-creates-wrong-map-values-for-enum-types-other-than-int32-or-int64.
The scripts included with the Semantic Logging Application Block to create a database for the SqlDatabaseSink only support SQL Server 2008 or higher, SQL Server LocalDB, Windows Azure SQL Database.
Localized event source using EventSourceAttribute.LocalizationResources when using Semantic Logging Application Block in process is not currently supported.
The Logging Application Block declarative configuration does not support runtime configuration changes.
If you are writing to the Windows Event Log using the Logging Application Block from an application that does not run with admin rights, you must ensure that you add the event source first by using the following PowerShell command:

New-EventLog -LogName Application -Source 'Enterprise Library Logging'

Documentation has not been tested for this release and the final documentation will be available later.
QuickStarts and sample code included have not been extensively tested. For example, they have not been tested for performance, security, globalization, and accessibility.

Change Log

Breaking Changes

The EnterpriseLibraryContainer class no longer exists. You must now explicitly bootstrap the blocks in your code now that Enterprise Library no longer relies on Unity to perform this function.
Support for configuration using Group Policy has been removed from this release.
Instrumentation has been removed from the blocks in this release.
Enterprise Library no longer uses the Unity Dependency Injection (DI) container to build Enterprise Library objects for your application. In this release, each block includes factories to build the Enterprise Library objects and/or static facades to access the Enterprise Library functionality. This change only affects the way that you instantiate the Enterprise Library objects you use in your application, it does not affect the functionality of those objects.
The WMI trace listener has been removed from the Logging Application Block.

Global Changes

All the blocks have been updated to the .NET 4.5 Framework.
All of the blocks have new bootstrapping methods that do not rely on Unity.
The dependency on Unity has been removed from all blocks including Common. The only exception is the Policy Injection Application Block which takes a dependency on Unity.Interception.

Deprecated Blocks

The following blocks have been deprecated and removed from the Enterprise Library.

Caching Application Block
Cryptography Application Block
Security Application Block

New Blocks

Enterprise Library includes the following new blocks.

Semantic Logging Application Block
Transient Fault Handling Application Block (this block was previously a part of the Enterprise Library Integration Pack for Windows Azure)

Data Access Application Block

The provided SQL Server scripts now support SQL Server 2005 or later. In previous versions of Enterprise Library, the scripts supported SQL Server 2000 or later.
The tests for the Data Access Application Block now use Microsoft SQL Server 2012 Express LocalDB.
Data Access Application Block objects can be created directly from configuration without using a DI container.
The OracleClient data provider is deprecated in version 4.5 of the .NET Framework; features in the current version of Enterprise Library that rely on this data provider are also deprecated. These features may be removed in a subsequent release of Enterprise Library.

Exception Handling Application Block

Exception Handling Application Block objects can be created directly from configuration without using a DI container.

Logging Application Block

Rolling Behavior

The behavior of the RollingFlatFileTraceListener class has changed when the file is set to roll at midnight.
Take the following scenario:

On Monday, trace message #1 is written by the RollingFlatFileTraceListener trace listener.
On Tuesday, no trace messages are written to the log.
On Wednesday, no trace messages are written to the log.
On Thursday, trace message #2 is written by the RollingFlatFileTraceListener trace listener.

Previously trace message #1 would have appeared in a log file dated Wednesday, because the RollingFlatFileTraceListener trace listener rolled the log when it wrote a message.
Now, trace message #1 appears in a log file dated Monday, because the RollingFlatFileTraceListener trace listener rolls the log every day at midnight.

JSON Formatter

The Logging Application Block now includes a JSON formatter.

The WmiTraceListener Class

The WmiTraceListener class has been removed from this block.

Email Event Listener

Fixed several bugs that resulted in null reference exceptions being thrown when providing invalid configuration data for the email event listener.

MSMQ Event Listener

More error checking for configuration settings was added to this listener.
A new constructor was added to facilitate creating MSMQ event listener objects.

Rolling Flat File Event Listener

A new constructor was added to facilitate creating rolling flat file event listener objects.

Asynchronous Support

You can now use the existing listeners to write log messages asynchronously.

Semantic Logging Application Block

The internal implementation has changed since the CTP release. The event listener implementations have been replaced by a set of Sink classes and an ObservableEventListener class. This has decoupled the event destinations from the event listener and enabled additional extensibility scenarios.
The database schema has changed since the CTP release. You will need to recreate any logging databases using the DatabaseSink.sql script.
The GenericDatabaseSink has been removed from the block since the CTP release.

Transient Fault Handling Application Block

The following changes have been made to the Transient Fault Handling Application Block since it was released as part of the Enterprise Library Integration Pack for Windows Azure.

Added support for Windows Azure Caching
Added support for Windows Azure Storage 2.0. However, if you are using version 2 of the Windows Azure Storage Client Library, it is recommended that you use the built-in retry policies in the Windows Azure Storage Client Library in preference to the retry policies for the Windows Azure Storage Service in the Transient Fault Handling Application Block.
Updated to support Windows Azure Service Bus 1.8
Error code 40540 from SQL Database added as a transient error (see http://msdn.microsoft.com/en-us/library/ff394106.aspx#bkmk_throt_errors).
Added error codes 10928 and 10929 from SQL Database as transient errors (see http://blogs.msdn.com/b/psssql/archive/2012/10/31/worker-thread-governance-coming-to-azure-sql-database.aspx).
Windows Azure storage account not found is no longer treated as a transient fault.
Fixed bug whereby an attempt to load an assembly resulted in a retry on failure.
The obsolete asynchronous overloads of the RetryPolicy.ExecuteAction method have been removed. You should use the RetryPolicy.ExecuteAsync method instead.

The classes located in the namespaces in the following list can now be found in Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling:

Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.SqlAzure
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.ServiceBus
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.AzureStorage
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.Configuration
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.Cache

The PowerShell script Update-EntlibConfiguration.ps1 updates the configuration files in an existing project to reflect the changes in namespaces. Visual Studio tools help you fix your code when it detects the changed namespaces.

Policy Injection Application Block

The call handlers have been moved from the individual blocks in the Policy Injection Application Block.

Validation Application Block

The Unity assembly is now Security Transparent.
Unity now supports NetCore (Windows Store apps).
The bug that caused a first chance exception when registering a singleton is fixed.
The bug that resulted in static properties not being filtered out when doing property injection is fixed.
Internally, the WinRT namespaces that support Unity in Windows Store apps have been renamed to NetCore.
Unity now supports resolving objects of type Lazy<T>
Unity now supports registration by convention through the new RegisterTypes method.
Unity now includes support for ASP.NET MVC and ASP.NET Web API.

Updated Wiki: EntLib6ReleaseNotes

dominicbetts — Thu, 16 May 2013 07:41:11 GMT

Microsoft Enterprise Library 6 – Final Release

Release Notes

Where to get it?

Via NuGet – use the NuGet Package Manager in Visual Studio and search online for the “enterpriselibrary” packages. Pick the official Microsoft packages.

What’s New in this Release?

This major release of Enterprise Library contains many compelling new features and updates that will make developers more productive. These include:

Major changes throughout Enterprise Library to make it simpler and easier to learn and use whilst minimizing the impact of these changes for existing users.
A new Semantic Logging Application Block to make it easier to adopt semantic/structured logging in your applications.
The addition of the Transient Fault Handling Block as a full member of the library to help you make your on-premises and Windows Azure based applications more resilient to transient errors.
Several enhancements to Unity type registration to help you streamline the registration of types in the Unity container.
Support for Windows Store apps.
Simpler programmatic configuration for all the blocks.
Deeper integration with other technologies such as ASP.NET MVC and WebApi.

The detailed change log is included in the Enterprise Library documentation and also at the end of this document.

Installing with Previous Versions of Enterprise Library

You cannot install Enterprise Library 6 side-by-side with a previous version of the library in the same Visual Studio project.

System requirements

Supported architectures: x86 and x64.
Operating systems: Microsoft Windows® 8, Microsoft Windows® 7, Windows Server 2008 R2, Windows Server 2012.
Supported .NET Frameworks: Microsoft .NET Framework 4.5, .NET for Windows Store Apps (previously known as WinRT) for Unity and the Transient Fault Handling Application Block.
Rich development environment: Microsoft Visual Studio 2012, Professional, Ultimate, or Express editions. The database setup scripts depend on the SQL Server Data Tools that are included in a standard installation of Visual Studio.

For the Data Access Application Block, the following is also required:

A database server running a database that is supported by a .NET Framework 4.5 data provider.

For the Logging Application Block, the following may be required:

If you are using the Message Queuing (MSMQ) Trace Listener to store log messages, you need the Microsoft Message Queuing (MSMQ) components installed.
If you are using the Database Trace Listener to store log messages, you need access to a database server.
If you are using the E-mail Trace Listener to store log messages, you need access to an SMTP server.

For the Semantic Logging Application Block, the following may be required:

If you are using the SQL Database Sink to store log messages, you need access to a SQL Server database server. The following are supported: SQL Server 2008 and higher, SQL Server LocalDB, Windows Azure SQL Database.
If you are using the Windows Azure Sink to store log messages, you need access to a Windows Azure storage account.

For the Transient Fault Handling Application Block, the following is required to install the NuGet package:

NuGet 2.2. This is included in Visual Studio 2012 Update 2. Once the package is downloaded, you can copy the assemblies to a machine that does not have NuGet 2.2 and use the block there.

If these dependencies are not met, you may not be able to use certain Enterprise Library features.

Learning More

The following learning resources are recommended:

Enterprise Library Reference Documentation
Unity Reference Documentation
Enterprise Library Developer’s Guide
Unity Developer’s Guide
Migration Guide
Hands-on Labs (available later)
Discussion forum

Providing feedback

Support

Community support is provided via Enterprise Library Codeplex forum.

Known Issues

If you are using the Transient Fault Handling Application Block, you should ensure that you are using version 4.0.30319.18003 or later of mscorlib.dll, otherwise you may see a VerificationException exception at run time. For more information, see http://support.microsoft.com/kb/2748646.
If you are using the Transient Fault Handling Application Block, you must have NuGet 2.2 in order to install the NuGet package. Note that this update is included in Visual Studio 2012, Update 2.
To run the coded UI tests in the Reference Implementation solutions, you must have the Visual Studio 2012 Ultimate edition.
The Semantic Logging Application Block uses the TraceEvent library (http://bcl.codeplex.com/wikipage?title=TraceEvent) internally. The Globalization Warnings reported by FxCop static analysis in this library have not been addressed.
The Semantic Logging Application Block running out-of-process only supports logging events authored using the managed EventSource class.
Using the Semantic Logging Application Block, you should not new up a listener, write a log message, and the dispose the listener. The typical usage pattern is to initialize listeners during application start up, log messages while the application is running, and then dispose the listeners during application shutdown.
When you author a custom EventSource to use with the Semantic Logging Application Block, you should only use enum types of int32 or int64. For more information, see http://connect.microsoft.com/VisualStudio/feedback/details/785409/eventsource-manifest-generation-creates-wrong-map-values-for-enum-types-other-than-int32-or-int64.
The scripts included with the Semantic Logging Application Block to create a database for the SqlDatabaseSink only support SQL Server 2008 or higher, SQL Server LocalDB, Windows Azure SQL Database.
Localized event source using EventSourceAttribute.LocalizationResources when using Semantic Logging Application Block in process is not currently supported.
The Logging Application Block declarative configuration does not support runtime configuration changes.
If you are writing to the Windows Event Log using the Logging Application Block from an application that does not run with admin rights, you must ensure that you add the event source first by using the following PowerShell command:

New-EventLog -LogName Application -Source 'Enterprise Library Logging'

Documentation has not been tested for this release and the final documentation will be available later.
QuickStarts and sample code included have not been extensively tested.

Change Log

Breaking Changes

The EnterpriseLibraryContainer class no longer exists. You must now explicitly bootstrap the blocks in your code now that Enterprise Library no longer relies on Unity to perform this function.
Support for configuration using Group Policy has been removed from this release.
Instrumentation has been removed from the blocks in this release.
Enterprise Library no longer uses the Unity Dependency Injection (DI) container to build Enterprise Library objects for your application. In this release, each block includes factories to build the Enterprise Library objects and/or static facades to access the Enterprise Library functionality. This change only affects the way that you instantiate the Enterprise Library objects you use in your application, it does not affect the functionality of those objects.
The WMI trace listener has been removed from the Logging Application Block.

Global Changes

All the blocks have been updated to the .NET 4.5 Framework.
All of the blocks have new bootstrapping methods that do not rely on Unity.
The dependency on Unity has been removed from all blocks including Common. The only exception is the Policy Injection Application Block which takes a dependency on Unity.Interception.

Deprecated Blocks

The following blocks have been deprecated and removed from the Enterprise Library.

Caching Application Block
Cryptography Application Block
Security Application Block

New Blocks

Enterprise Library includes the following new blocks.

Semantic Logging Application Block
Transient Fault Handling Application Block (this block was previously a part of the Enterprise Library Integration Pack for Windows Azure)

Data Access Application Block

Exception Handling Application Block

Exception Handling Application Block objects can be created directly from configuration without using a DI container.

Logging Application Block

Rolling Behavior

The behavior of the RollingFlatFileTraceListener class has changed when the file is set to roll at midnight.
Take the following scenario:

On Monday, trace message #1 is written by the RollingFlatFileTraceListener trace listener.
On Tuesday, no trace messages are written to the log.
On Wednesday, no trace messages are written to the log.
On Thursday, trace message #2 is written by the RollingFlatFileTraceListener trace listener.

JSON Formatter

The Logging Application Block now includes a JSON formatter.

The WmiTraceListener Class

The WmiTraceListener class has been removed from this block.

Email Event Listener

Fixed several bugs that resulted in null reference exceptions being thrown when providing invalid configuration data for the email event listener.

MSMQ Event Listener

More error checking for configuration settings was added to this listener.
A new constructor was added to facilitate creating MSMQ event listener objects.

Rolling Flat File Event Listener

A new constructor was added to facilitate creating rolling flat file event listener objects.

Asynchronous Support

You can now use the existing listeners to write log messages asynchronously.

Semantic Logging Application Block

Transient Fault Handling Application Block

The following changes have been made to the Transient Fault Handling Application Block since it was released as part of the Enterprise Library Integration Pack for Windows Azure.

Added support for Windows Azure Caching
Added support for Windows Azure Storage 2.0. However, if you are using version 2 of the Windows Azure Storage Client Library, it is recommended that you use the built-in retry policies in the Windows Azure Storage Client Library in preference to the retry policies for the Windows Azure Storage Service in the Transient Fault Handling Application Block.
Updated to support Windows Azure Service Bus 1.8
Error code 40540 from SQL Database added as a transient error (see http://msdn.microsoft.com/en-us/library/ff394106.aspx#bkmk_throt_errors).
Added error codes 10928 and 10929 from SQL Database as transient errors (see http://blogs.msdn.com/b/psssql/archive/2012/10/31/worker-thread-governance-coming-to-azure-sql-database.aspx).
Windows Azure storage account not found is no longer treated as a transient fault.
Fixed bug whereby an attempt to load an assembly resulted in a retry on failure.
The obsolete asynchronous overloads of the RetryPolicy.ExecuteAction method have been removed. You should use the RetryPolicy.ExecuteAsync method instead.

The classes located in the namespaces in the following list can now be found in Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling:

Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.SqlAzure
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.ServiceBus
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.AzureStorage
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.Configuration
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.Cache

Policy Injection Application Block

The call handlers have been moved from the individual blocks in the Policy Injection Application Block.

Validation Application Block

The Unity assembly is now Security Transparent.
Unity now supports NetCore (Windows Store apps).
The bug that caused a first chance exception when registering a singleton is fixed.
The bug that resulted in static properties not being filtered out when doing property injection is fixed.
Internally, the WinRT namespaces that support Unity in Windows Store apps have been renamed to NetCore.
Unity now supports resolving objects of type Lazy<T>
Unity now supports registration by convention through the new RegisterTypes method.
Unity now includes support for ASP.NET MVC and ASP.NET Web API.

Updated Wiki: EntLib6ReleaseNotes

dominicbetts — Thu, 16 May 2013 05:30:55 GMT

Microsoft Enterprise Library 6 – Final Release

Release Notes

Where to get it?

Via NuGet – use the NuGet Package Manager in Visual Studio and search online for the “enterpriselibrary” packages. Pick the official Microsoft packages.

What’s New in this Release?

This major release of Enterprise Library contains many compelling new features and updates that will make developers more productive. These include:

Major changes throughout Enterprise Library to make it simpler and easier to learn and use whilst minimizing the impact of these changes for existing users.
A new Semantic Logging Application Block to make it easier to adopt semantic/structured logging in your applications.
The addition of the Transient Fault Handling Block as a full member of the library to help you make your on-premises and Windows Azure based applications more resilient to transient errors.
Several enhancements to Unity type registration to help you streamline the registration of types in the Unity container.
Support for Windows Store apps.
Simpler programmatic configuration for all the blocks.
Deeper integration with other technologies such as ASP.NET MVC and WebApi.

The detailed change log is included in the Enterprise Library documentation and also at the end of this document.

Installing with Previous Versions of Enterprise Library

You cannot install Enterprise Library 6 side-by-side with a previous version of the library in the same Visual Studio project.

System requirements

Supported architectures: x86 and x64.
Operating systems: Microsoft Windows® 8, Microsoft Windows® 7, Windows Server 2008 R2, Windows Server 2012.
Supported .NET Frameworks: Microsoft .NET Framework 4.5, .NET for Windows Store Apps (previously known as WinRT) for Unity and the Transient Fault Handling Application Block.
Rich development environment: Microsoft Visual Studio 2012, Professional, Ultimate, or Express editions. The database setup scripts depend on the SQL Server Data Tools that are included in a standard installation of Visual Studio.

For the Data Access Application Block, the following is also required:

A database server running a database that is supported by a .NET Framework 4.5 data provider.

For the Logging Application Block, the following may be required:

If you are using the Message Queuing (MSMQ) Trace Listener to store log messages, you need the Microsoft Message Queuing (MSMQ) components installed.
If you are using the Database Trace Listener to store log messages, you need access to a database server.
If you are using the E-mail Trace Listener to store log messages, you need access to an SMTP server.

For the Semantic Logging Application Block, the following may be required:

If you are using the SQL Database Sink to store log messages, you need access to a SQL Server database server. The following are supported: SQL Server 2008 and higher, SQL Server LocalDB, Windows Azure SQL Database.
If you are using the Windows Azure Sink to store log messages, you need access to a Windows Azure storage account.

For the Transient Fault Handling Application Block, the following is required to install the NuGet package:

NuGet 2.2. This is included in Visual Studio 2012 Update 2. Once the package is downloaded, you can copy the assemblies to a machine that does not have NuGet 2.2 and use the block there.

If these dependencies are not met, you may not be able to use certain Enterprise Library features.

Learning More

The following learning resources are recommended:

Enterprise Library Reference Documentation
Unity Reference Documentation
Enterprise Library Developer’s Guide
Unity Developer’s Guide
Migration Guide
Hands-on Labs (available later)
Discussion forum

Providing feedback

Support

Community support is provided via Enterprise Library Codeplex forum.

Known Issues

If you are using the Transient Fault Handling Application Block, you should ensure that you are using version 4.0.30319.18003 or later of mscorlib.dll, otherwise you may see a VerificationException exception at run time. For more information, see http://support.microsoft.com/kb/2748646.
If you are using the Transient Fault Handling Application Block, you must have NuGet 2.2 in order to install the NuGet package. Note that this update is included in Visual Studio 2012, Update 2.
To run the coded UI tests in the Reference Implementation solutions, you must have the Visual Studio 2012 Ultimate edition.
The Semantic Logging Application Block uses the TraceEvent library (http://bcl.codeplex.com/wikipage?title=TraceEvent) internally. The Globalization Warnings reported by FxCop static analysis in this library have not been addressed.
The Semantic Logging Application Block running out-of-process only supports logging events authored using the managed EventSource class.
Using the Semantic Logging Application Block, you should not new up a listener, write a log message, and the dispose the listener. The typical usage pattern is to initialize listeners during application start up, log messages while the application is running, and then dispose the listeners during application shutdown.
When you author a custom EventSource to use with the Semantic Logging Application Block, you should only use enum types of int32 or int64. For more information, see http://connect.microsoft.com/VisualStudio/feedback/details/785409/eventsource-manifest-generation-creates-wrong-map-values-for-enum-types-other-than-int32-or-int64.
The scripts included with the Semantic Logging Application Block to create a database for the SqlDatabaseSink only support SQL Server 2008 or higher, SQL Server LocalDB, Windows Azure SQL Database.
Localized event source using EventSourceAttribute.LocalizationResources when using Semantic Logging Application Block in process is not currently supported.
The Logging Application Block declarative configuration does not support runtime configuration changes.
If you are writing to the Windows Event Log using the Logging Application Block from an application that does not run with admin rights, you must ensure that you add the event source first by using the following PowerShell command:

New-EventLog -LogName Application -Source 'Enterprise Library Logging'

Documentation has not been tested for this release and the final documentation will be available later.
QuickStarts and sample code included have not been extensively tested.

Change Log

Breaking Changes

The EnterpriseLibraryContainer class no longer exists. You must now explicitly bootstrap the blocks in your code now that Enterprise Library no longer relies on Unity to perform this function.
Support for configuration using Group Policy has been removed from this release.
Instrumentation has been removed from the blocks in this release.
Enterprise Library no longer uses the Unity Dependency Injection (DI) container to build Enterprise Library objects for your application. In this release, each block includes factories to build the Enterprise Library objects and/or static facades to access the Enterprise Library functionality. This change only affects the way that you instantiate the Enterprise Library objects you use in your application, it does not affect the functionality of those objects.
The WMI trace listener has been removed from the Logging Application Block.

Global Changes

All the blocks have been updated to the .NET 4.5 Framework.
All of the blocks have new bootstrapping methods that do not rely on Unity.
The dependency on Unity has been removed from all blocks including Common. The only exception is the Policy Injection Application Block which takes a dependency on Unity.Interception.

Deprecated Blocks

The following blocks have been deprecated and removed from the Enterprise Library.

Caching Application Block
Cryptography Application Block
Security Application Block

New Blocks

Enterprise Library includes the following new blocks.

Semantic Logging Application Block
Transient Fault Handling Application Block (this block was previously a part of the Enterprise Library Integration Pack for Windows Azure)

Data Access Application Block

Exception Handling Application Block

Exception Handling Application Block objects can be created directly from configuration without using a DI container.

Logging Application Block

Rolling Behavior

The behavior of the RollingFlatFileTraceListener class has changed when the file is set to roll at midnight.
Take the following scenario:

On Monday, trace message #1 is written by the RollingFlatFileTraceListener trace listener.
On Tuesday, no trace messages are written to the log.
On Wednesday, no trace messages are written to the log.
On Thursday, trace message #2 is written by the RollingFlatFileTraceListener trace listener.

JSON Formatter

The Logging Application Block now includes a JSON formatter.

The WmiTraceListener Class

The WmiTraceListener class has been removed from this block.

Email Event Listener

Fixed several bugs that resulted in null reference exceptions being thrown when providing invalid configuration data for the email event listener.

MSMQ Event Listener

More error checking for configuration settings was added to this listener.
A new constructor was added to facilitate creating MSMQ event listener objects.

Rolling Flat File Event Listener

A new constructor was added to facilitate creating rolling flat file event listener objects.

Asynchronous Support

You can now use the existing listeners to write log messages asynchronously.

Semantic Logging Application Block

Transient Fault Handling Application Block

The following changes have been made to the Transient Fault Handling Application Block since it was released as part of the Enterprise Library Integration Pack for Windows Azure.

Added support for Windows Azure Caching
Added support for Windows Azure Storage 2.0
Updated to support Windows Azure Service Bus 1.8
Error code 40540 from SQL Database added as a transient error (see http://msdn.microsoft.com/en-us/library/ff394106.aspx#bkmk_throt_errors).
Added error codes 10928 and 10929 from SQL Database as transient errors (see http://blogs.msdn.com/b/psssql/archive/2012/10/31/worker-thread-governance-coming-to-azure-sql-database.aspx).
Windows Azure storage account not found is no longer treated as a transient fault.
Fixed bug whereby an attempt to load an assembly resulted in a retry on failure.
The obsolete asynchronous overloads of the RetryPolicy.ExecuteAction method have been removed. You should use the RetryPolicy.ExecuteAsync method instead.

The classes located in the namespaces in the following list can now be found in Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling:

Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.SqlAzure
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.ServiceBus
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.AzureStorage
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.Configuration
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.Cache

Policy Injection Application Block

The call handlers have been moved from the individual blocks in the Policy Injection Application Block.

Validation Application Block

The Unity assembly is now Security Transparent.
Unity now supports NetCore (Windows Store apps).
The bug that caused a first chance exception when registering a singleton is fixed.
The bug that resulted in static properties not being filtered out when doing property injection is fixed.
Internally, the WinRT namespaces that support Unity in Windows Store apps have been renamed to NetCore.
Unity now supports resolving objects of type Lazy<T>
Unity now supports registration by convention through the new RegisterTypes method.
Unity now includes support for ASP.NET MVC and ASP.NET Web API.

Updated Wiki: Home

gmelnik — Tue, 07 May 2013 00:42:24 GMT

The Microsoft Enterprise Library is a collection of reusable software components (application blocks) designed to assist software developers with common enterprise development challenges. Application blocks are provided as source code plus documentation that can be used "as is," extended, or modified by developers to use on complex, enterprise-level line-of-business development projects.

DOWNLOAD	Official releases	PREVIEW	Current Roadmap, Past Roadmaps
	Current release - April 2010 (5.0), Silverlight Integration Pack - May 2011, Windows Azure Integration Pack - Nov 2011, Previous releases		Enterprise Library 6.0
	Standalone Unity, Unity 2.1 - Aug 2012 Update, Unity 3.0 for .NET4.5 Preview		Follow @mspnp, @gmelnik and the #entlib hashtag
LEARN	Hands-on Labs	GET SUPPORT	Discussion Forum
	EntLib5 Developer's Guide		Issue Tracker
	Videos, Webcast Demos		Support How-to
	EntLib FAQ		Sample Projects
	Reference documentation
CONTRIBUTE	Share extensions via EntLibContrib Project (Jan 2010 Release)	PROVIDE FEEDBACK	EntLib satisfaction survey
	Hosting your extension in your own CodePlex project? Tag it with Enterprise Library		Submit suggestions
			Report bugs

News

Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library News Feed

Just released - Microsoft Enterprise Library 6

Friday, April 26, 2013 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Embracing Semantic Logging

Thursday, February 07, 2013 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Enterprise Library 6.0 - Vision/Scope

Thursday, November 08, 2012 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Enterprise Library vNext - Simplified!

Thursday, August 23, 2012 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Transient Fault Handling Application Block (Topaz) updates

Tuesday, August 21, 2012 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Announcing the Enterprise Library Integration Pack for Windows Azure with Autoscaling, Transient Fault Handling and more

Friday, December 02, 2011 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Unity 3.0 Preview for .NET 4.5

Friday, October 28, 2011 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Windows Azure Autoscaling Block BETA is out

Friday, October 14, 2011 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

WASABi scale groups

Friday, October 07, 2011 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Announcing Windows Azure Autoscaling Block preview

Monday, September 12, 2011 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library News Feed

Software Mechanics News Feed

Entlib 5.0 Hands-on labs released

Tuesday, May 25, 2010 | From Software Mechanics

Entlib 5.0 Hands-on labs released

Tuesday, May 25, 2010 | From Software Mechanics

Unity 2.0, Entlib Docs released

Wednesday, May 05, 2010 | From Software Mechanics

Catching up with recent stuff

Sunday, May 02, 2010 | From Software Mechanics

End of an era

Saturday, April 03, 2010 | From Software Mechanics

Software Mechanics News Feed

Notes From the Team Room : Enterprise Library News Feed

Enterprise Library 5.0: Some Architecture Changes

Wednesday, June 24, 2009 | From Notes From the Team Room : Enterprise Library

Enterprise Library 5.0: Some Architecture Changes

Wednesday, June 24, 2009 | From Notes From the Team Room : Enterprise Library

Enterprise Library Needs Your Vote

Friday, March 27, 2009 | From Notes From the Team Room : Enterprise Library

Notes From the Team Room : Enterprise Library News Feed

Writing ... or Just Practicing? : Enterprise Library News Feed

Try, Try, and Try Again

Sunday, February 12, 2012 | From Writing ... or Just Practicing? : Enterprise Library

Additional Integrational Hybridization

Sunday, October 09, 2011 | From Writing ... or Just Practicing? : Enterprise Library

Hybrid Triangulation (with Cat Food and Bananas)

Monday, September 26, 2011 | From Writing ... or Just Practicing? : Enterprise Library

Time to Stop Typing and Start Thinking

Monday, September 12, 2011 | From Writing ... or Just Practicing? : Enterprise Library

It Configures

Sunday, May 09, 2010 | From Writing ... or Just Practicing? : Enterprise Library

Writing ... or Just Practicing? : Enterprise Library News Feed

patterns & practices Links

Updated Wiki: Videos

gmelnik — Tue, 07 May 2013 00:42:00 GMT

Enterprise Library Videos

This page contains video tutorials about using Enterprise Library. If you have created any videos which you would like to include on this page, please let us know!
Also, check out these Channel9 videos

Enterprise Library 5.0 Silverlight Integration Pack

Validation Application Block for Silverlight Demo by Grigori Melnik and Chris Tavares (15 minutes)
Cross-iter validation with Silverlight Integration Pack Demo by Grigori Melnik and Erwin van der Valk (30 minutes)
Unity Interception for Silverlight Demo by Grigori Melnik and Chris Tavares (34 minutes)
Silverlight Logging Demo by Fernando Simonazzi and Grigori Melnik (35 minutes)
Data Caching Demo by Erwin van der Valk and Grigori Melnik (31 minutes)

Enterprise Library 5.0

Enterprise Library5.0 Preview by Grigori Melnik and Bob Brumfield (54 minutes), hi res (~700MB)
What's Coming in Enterprise Library 5.0 by Grigori Melnik and Chris Tavares (15 minutes)
Enterprise Library 5.0 Pluralcast podcast with Chris Tavares and David Starr (44 minutes)

Policy Injection Application Block

Policy Injection Application Block ASP.NET Caching Screencast by David Hayden (8 minutes)

Validation Application Block

Validation Application Block ASP.NET Integration Screencast by David Hayden (15 minutes)

Updated Wiki: Webcast Demos

gmelnik — Tue, 07 May 2013 00:41:12 GMT

Demo Files from webcasts

We'll be placing copies of the demos we use in our EntLib webcasts here for folks to download.

StockTrade RI (updated), Apr 21, 2011
- Used in the Cross-tier validation demo (Mar 8, 2011) and the Data caching demo (Apr 21, 2011)
- http://entlib.codeplex.com/releases/view/64923

Silverlight Logging demo, Mar 30, 2011
- http://entlib.codeplex.com/releases/view/63549

Unity Interception demo, Mar 21, 2011
- http://entlib.codeplex.com/releases/view/62958

TransportController - a demo using Validation Application Block for Silverlight, Feb 17, 2011
- http://entlib.codeplex.com/releases/view/61159

Taking Advantage of Entlib 4 Webcast, July 10, 2008
- Entlib4WebcastDemo.zip

PIAB Webcast, May 8, 2007
- PIABDemos.zip

Updated Wiki: Home

gmelnik — Tue, 07 May 2013 00:40:48 GMT

DOWNLOAD	Official releases	PREVIEW	Current Roadmap, Past Roadmaps
	Current release - April 2010 (5.0), Silverlight Integration Pack - May 2011, Windows Azure Integration Pack - Nov 2011, Previous releases		Enterprise Library 6.0
	Standalone Unity, Unity 2.1 - Aug 2012 Update, Unity 3.0 for .NET4.5 Preview		Follow @mspnp, @gmelnik and the #entlib hashtag
LEARN	Hands-on Labs	GET SUPPORT	Discussion Forum
	EntLib5 Developer's Guide		Issue Tracker
	Videos, Webcast Demos		Support How-to
	EntLib FAQ		Sample Projects
	Reference documentation
CONTRIBUTE	Share extensions via EntLibContrib Project (Jan 2010 Release)	PROVIDE FEEDBACK	EntLib satisfaction survey
	Hosting your extension in your own CodePlex project? Tag it with Enterprise Library		Submit suggestions
			Report bugs

News

Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library News Feed

Just released - Microsoft Enterprise Library 6

Friday, April 26, 2013 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Embracing Semantic Logging

Thursday, February 07, 2013 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Enterprise Library 6.0 - Vision/Scope

Thursday, November 08, 2012 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Enterprise Library vNext - Simplified!

Thursday, August 23, 2012 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Transient Fault Handling Application Block (Topaz) updates

Tuesday, August 21, 2012 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Announcing the Enterprise Library Integration Pack for Windows Azure with Autoscaling, Transient Fault Handling and more

Friday, December 02, 2011 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Unity 3.0 Preview for .NET 4.5

Friday, October 28, 2011 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Windows Azure Autoscaling Block BETA is out

Friday, October 14, 2011 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

WASABi scale groups

Friday, October 07, 2011 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Announcing Windows Azure Autoscaling Block preview

Monday, September 12, 2011 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library News Feed

Software Mechanics News Feed

Entlib 5.0 Hands-on labs released

Tuesday, May 25, 2010 | From Software Mechanics

Entlib 5.0 Hands-on labs released

Tuesday, May 25, 2010 | From Software Mechanics

Unity 2.0, Entlib Docs released

Wednesday, May 05, 2010 | From Software Mechanics

Catching up with recent stuff

Sunday, May 02, 2010 | From Software Mechanics

End of an era

Saturday, April 03, 2010 | From Software Mechanics

Software Mechanics News Feed

Notes From the Team Room : Enterprise Library News Feed

Enterprise Library 5.0: Some Architecture Changes

Wednesday, June 24, 2009 | From Notes From the Team Room : Enterprise Library

Enterprise Library 5.0: Some Architecture Changes

Wednesday, June 24, 2009 | From Notes From the Team Room : Enterprise Library

Enterprise Library Needs Your Vote

Friday, March 27, 2009 | From Notes From the Team Room : Enterprise Library

Notes From the Team Room : Enterprise Library News Feed

Writing ... or Just Practicing? : Enterprise Library News Feed

Try, Try, and Try Again

Sunday, February 12, 2012 | From Writing ... or Just Practicing? : Enterprise Library

Additional Integrational Hybridization

Sunday, October 09, 2011 | From Writing ... or Just Practicing? : Enterprise Library

Hybrid Triangulation (with Cat Food and Bananas)

Monday, September 26, 2011 | From Writing ... or Just Practicing? : Enterprise Library

Time to Stop Typing and Start Thinking

Monday, September 12, 2011 | From Writing ... or Just Practicing? : Enterprise Library

It Configures

Sunday, May 09, 2010 | From Writing ... or Just Practicing? : Enterprise Library

Writing ... or Just Practicing? : Enterprise Library News Feed

patterns & practices Links

Updated Wiki: EntLib6ReleaseNotes

dominicbetts — Fri, 03 May 2013 10:02:02 GMT

Microsoft Enterprise Library 6 – Final Release

Release Notes

Where to get it?

Via NuGet – use the NuGet Package Manager in Visual Studio and search online for the “enterpriselibrary” packages. Pick the official Microsoft packages.

What’s New in this Release?

This major release of Enterprise Library contains many compelling new features and updates that will make developers more productive. These include:

Major changes throughout Enterprise Library to make it simpler and easier to learn and use whilst minimizing the impact of these changes for existing users.
A new Semantic Logging Application Block to make it easier to adopt semantic/structured logging in your applications.
The addition of the Transient Fault Handling Block as a full member of the library to help you make your on-premises and Windows Azure based applications more resilient to transient errors.
Several enhancements to Unity type registration to help you streamline the registration of types in the Unity container.
Support for Windows Store apps.
Simpler programmatic configuration for all the blocks.
Deeper integration with other technologies such as ASP.NET MVC and WebApi.

The detailed change log is included in the Enterprise Library documentation and also at the end of this document.

Installing with Previous Versions of Enterprise Library

You cannot install Enterprise Library 6 side-by-side with a previous version of the library in the same Visual Studio project.

System requirements

Supported architectures: x86 and x64.
Operating systems: Microsoft Windows® 8, Microsoft Windows® 7, Windows Server 2008 R2, Windows Server 2012.
Supported .NET Frameworks: Microsoft .NET Framework 4.5, .NET for Windows Store Apps (previously known as WinRT) for Unity and the Transient Fault Handling Application Block.
Rich development environment: Microsoft Visual Studio 2012, Professional, Ultimate, or Express editions.

For the Data Access Application Block, the following is also required:

A database server running a database that is supported by a .NET Framework 4.5 data provider.

For the Logging Application Block, the following may be required:

If you are using the Message Queuing (MSMQ) Trace Listener to store log messages, you need the Microsoft Message Queuing (MSMQ) components installed.
If you are using the Database Trace Listener to store log messages, you need access to a database server.
If you are using the E-mail Trace Listener to store log messages, you need access to an SMTP server.

For the Semantic Logging Application Block, the following may be required:

If you are using the SQL Database Sink to store log messages, you need access to a SQL Server database server. The following are supported: SQL Server 2008 and higher, SQL Server LocalDB, Windows Azure SQL Database.
If you are using the Windows Azure Sink to store log messages, you need access to a Windows Azure storage account.

For the Transient Fault Handling Application Block, the following is required to install the NuGet package:

NuGet 2.2. This is included in Visual Studio 2012 Update 2. Once the package is downloaded, you can copy the assemblies to a machine that does not have NuGet 2.2 and use the block there.

If these dependencies are not met, you may not be able to use certain Enterprise Library features.

Learning More

The following learning resources are recommended:

Enterprise Library Reference Documentation
Unity Reference Documentation
Enterprise Library Developer’s Guide
Unity Developer’s Guide
Migration Guide
Hands-on Labs (available later)
Discussion forum

Providing feedback

Support

Community support is provided via Enterprise Library Codeplex forum.

Known Issues

If you are using the Transient Fault Handling Application Block, you should ensure that you are using version 4.0.30319.18003 or later of mscorlib.dll, otherwise you may see a VerificationException exception at run time. For more information, see http://support.microsoft.com/kb/2748646.
If you are using the Transient Fault Handling Application Block, you must have NuGet 2.2 in order to install the NuGet package. Note that this update is included in Visual Studio 2012, Update 2.
To run the coded UI tests in the Reference Implementation solutions, you must have the Visual Studio 2012 Ultimate edition.
The Semantic Logging Application Block uses the TraceEvent library (http://bcl.codeplex.com/wikipage?title=TraceEvent) internally. The Globalization Warnings reported by FxCop static analysis in this library have not been addressed.
The Semantic Logging Application Block running out-of-process only supports logging events authored using the managed EventSource class.
Using the Semantic Logging Application Block, you should not new up a listener, write a log message, and the dispose the listener. The typical usage pattern is to initialize listeners during application start up, log messages while the application is running, and then dispose the listeners during application shutdown.
When you author a custom EventSource to use with the Semantic Logging Application Block, you should only use enum types of int32 or int64. For more information, see http://connect.microsoft.com/VisualStudio/feedback/details/785409/eventsource-manifest-generation-creates-wrong-map-values-for-enum-types-other-than-int32-or-int64.
The scripts included with the Semantic Logging Application Block to create a database for the SqlDatabaseSink only support SQL Server 2008 or higher, SQL Server LocalDB, Windows Azure SQL Database.
Localized event source using EventSourceAttribute.LocalizationResources when using Semantic Logging Application Block in process is not currently supported.
The Logging Application Block declarative configuration does not support runtime configuration changes.
If you are writing to the Windows Event Log using the Logging Application Block from an application that does not run with admin rights, you must ensure that you add the event source first by using the following PowerShell command:

New-EventLog -LogName Application -Source 'Enterprise Library Logging'

Documentation has not been tested for this release and the final documentation will be available later.
QuickStarts and sample code included have not been extensively tested.

Change Log

Breaking Changes

The EnterpriseLibraryContainer class no longer exists. You must now explicitly bootstrap the blocks in your code now that Enterprise Library no longer relies on Unity to perform this function.
Support for configuration using Group Policy has been removed from this release.
Instrumentation has been removed from the blocks in this release.
Enterprise Library no longer uses the Unity Dependency Injection (DI) container to build Enterprise Library objects for your application. In this release, each block includes factories to build the Enterprise Library objects and/or static facades to access the Enterprise Library functionality. This change only affects the way that you instantiate the Enterprise Library objects you use in your application, it does not affect the functionality of those objects.
The WMI trace listener has been removed from the Logging Application Block.

Global Changes

All the blocks have been updated to the .NET 4.5 Framework.
All of the blocks have new bootstrapping methods that do not rely on Unity.
The dependency on Unity has been removed from all blocks including Common. The only exception is the Policy Injection Application Block which takes a dependency on Unity.Interception.

Deprecated Blocks

The following blocks have been deprecated and removed from the Enterprise Library.

Caching Application Block
Cryptography Application Block
Security Application Block

New Blocks

Enterprise Library includes the following new blocks.

Semantic Logging Application Block
Transient Fault Handling Application Block (this block was previously a part of the Enterprise Library Integration Pack for Windows Azure)

Data Access Application Block

Exception Handling Application Block

Exception Handling Application Block objects can be created directly from configuration without using a DI container.

Logging Application Block

Rolling Behavior

The behavior of the RollingFlatFileTraceListener class has changed when the file is set to roll at midnight.
Take the following scenario:

On Monday, trace message #1 is written by the RollingFlatFileTraceListener trace listener.
On Tuesday, no trace messages are written to the log.
On Wednesday, no trace messages are written to the log.
On Thursday, trace message #2 is written by the RollingFlatFileTraceListener trace listener.

JSON Formatter

The Logging Application Block now includes a JSON formatter.

The WmiTraceListener Class

The WmiTraceListener class has been removed from this block.

Email Event Listener

Fixed several bugs that resulted in null reference exceptions being thrown when providing invalid configuration data for the email event listener.

MSMQ Event Listener

More error checking for configuration settings was added to this listener.
A new constructor was added to facilitate creating MSMQ event listener objects.

Rolling Flat File Event Listener

A new constructor was added to facilitate creating rolling flat file event listener objects.

Asynchronous Support

You can now use the existing listeners to write log messages asynchronously.

Semantic Logging Application Block

Transient Fault Handling Application Block

The following changes have been made to the Transient Fault Handling Application Block since it was released as part of the Enterprise Library Integration Pack for Windows Azure.

Added support for Windows Azure Caching
Added support for Windows Azure Storage 2.0
Updated to support Windows Azure Service Bus 1.8
Error code 40540 from SQL Database added as a transient error (see http://msdn.microsoft.com/en-us/library/ff394106.aspx#bkmk_throt_errors).
Added error codes 10928 and 10929 from SQL Database as transient errors (see http://blogs.msdn.com/b/psssql/archive/2012/10/31/worker-thread-governance-coming-to-azure-sql-database.aspx).
Windows Azure storage account not found is no longer treated as a transient fault.
Fixed bug whereby an attempt to load an assembly resulted in a retry on failure.
The obsolete asynchronous overloads of the RetryPolicy.ExecuteAction method have been removed. You should use the RetryPolicy.ExecuteAsync method instead.

The classes located in the namespaces in the following list can now be found in Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling:

Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.SqlAzure
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.ServiceBus
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.AzureStorage
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.Configuration
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.Cache

Policy Injection Application Block

The call handlers have been moved from the individual blocks in the Policy Injection Application Block.

Validation Application Block

The Unity assembly is now Security Transparent.
Unity now supports NetCore (Windows Store apps).
The bug that caused a first chance exception when registering a singleton is fixed.
The bug that resulted in static properties not being filtered out when doing property injection is fixed.
Internally, the WinRT namespaces that support Unity in Windows Store apps have been renamed to NetCore.
Unity now supports resolving objects of type Lazy<T>
Unity now supports registration by convention through the new RegisterTypes method.
Unity now includes support for ASP.NET MVC and ASP.NET Web API.

Updated Wiki: EntLib6ReleaseNotes

dominicbetts — Thu, 02 May 2013 14:31:13 GMT

Microsoft Enterprise Library 6 – Final Release

Release Notes

Where to get it?

Via NuGet – use the NuGet Package Manager in Visual Studio and search online for the “enterpriselibrary” packages. Pick the official Microsoft packages.

What’s New in this Release?

This major release of Enterprise Library contains many compelling new features and updates that will make developers more productive. These include:

Major changes throughout Enterprise Library to make it simpler and easier to learn and use whilst minimizing the impact of these changes for existing users.
A new Semantic Logging Application Block to make it easier to adopt semantic/structured logging in your applications.
The addition of the Transient Fault Handling Block as a full member of the library to help you make your on-premises and Windows Azure based applications more resilient to transient errors.
Several enhancements to Unity type registration to help you streamline the registration of types in the Unity container.
Support for Windows Store apps.
Simpler programmatic configuration for all the blocks.
Deeper integration with other technologies such as ASP.NET MVC and WebApi.

The detailed change log is included in the Enterprise Library documentation and also at the end of this document.

Installing with Previous Versions of Enterprise Library

You cannot install Enterprise Library 6 side-by-side with a previous version of the library in the same Visual Studio project.

System requirements

Supported architectures: x86 and x64.
Operating systems: Microsoft Windows® 8, Microsoft Windows® 7, Windows Server 2008 R2, Windows Server 2012.
Supported .NET Frameworks: Microsoft .NET Framework 4.5, .NET for Windows Store Apps (previously known as WinRT) for Unity and the Transient Fault Handling Application Block.
Rich development environment: Microsoft Visual Studio 2012, Professional, Ultimate, or Express editions.

For the Data Access Application Block, the following is also required:

A database server running a database that is supported by a .NET Framework 4.5 data provider.

For the Logging Application Block, the following may be required:

If you are using the Message Queuing (MSMQ) Trace Listener to store log messages, you need the Microsoft Message Queuing (MSMQ) components installed.
If you are using the Database Trace Listener to store log messages, you need access to a database server.
If you are using the E-mail Trace Listener to store log messages, you need access to an SMTP server.

For the Semantic Logging Application Block, the following may be required:

If you are using the SQL Database Sink to store log messages, you need access to a SQL Server database server. The following are supported: SQL Server 2008 and higher, SQL Server LocalDB, Windows Azure SQL Database.
If you are using the Windows Azure Sink to store log messages, you need access to a Windows Azure storage account. You must also install the Windows Azure SDK Version 1.8.

For the Transient Fault Handling Application Block, the following is required to install the NuGet package:

NuGet 2.2. This is included in Visual Studio 2012 Update 2. Once the package is downloaded, you can copy the assemblies to a machine that does not have NuGet 2.2 and use the block there.

If these dependencies are not met, you may not be able to use certain Enterprise Library features.

Learning More

The following learning resources are recommended:

Enterprise Library Reference Documentation
Unity Reference Documentation
Enterprise Library Developer’s Guide
Unity Developer’s Guide
Migration Guide
Hands-on Labs (available later)
Discussion forum

Providing feedback

Support

Community support is provided via Enterprise Library Codeplex forum.

Known Issues

If you are using the Transient Fault Handling Application Block, you should ensure that you are using version 4.0.30319.18003 or later of mscorlib.dll, otherwise you may see a VerificationException exception at run time. For more information, see http://support.microsoft.com/kb/2748646.
If you are using the Transient Fault Handling Application Block, you must have NuGet 2.2 in order to install the NuGet package. Note that this update is included in Visual Studio 2012, Update 2.
To run the coded UI tests in the Reference Implementation solutions, you must have the Visual Studio 2012 Ultimate edition.
The Semantic Logging Application Block uses the TraceEvent library (http://bcl.codeplex.com/wikipage?title=TraceEvent) internally. The Globalization Warnings reported by FxCop static analysis in this library have not been addressed.
The Semantic Logging Application Block running out-of-process only supports logging events authored using the managed EventSource class.
Using the Semantic Logging Application Block, you should not new up a listener, write a log message, and the dispose the listener. The typical usage pattern is to initialize listeners during application start up, log messages while the application is running, and then dispose the listeners during application shutdown.
When you author a custom EventSource to use with the Semantic Logging Application Block, you should only use enum types of int32 or int64. For more information, see http://connect.microsoft.com/VisualStudio/feedback/details/785409/eventsource-manifest-generation-creates-wrong-map-values-for-enum-types-other-than-int32-or-int64.
The scripts included with the Semantic Logging Application Block to create a database for the SqlDatabaseSink only support SQL Server 2008 or higher, SQL Server LocalDB, Windows Azure SQL Database.
Localized event source using EventSourceAttribute.LocalizationResources when using Semantic Logging Application Block in process is not currently supported.
The Logging Application Block declarative configuration does not support runtime configuration changes.
If you are writing to the Windows Event Log using the Logging Application Block from an application that does not run with admin rights, you must ensure that you add the event source first by using the following PowerShell command:

New-EventLog -LogName Application -Source 'Enterprise Library Logging'

Documentation has not been tested for this release and the final documentation will be available later.
QuickStarts and sample code included have not been extensively tested.

Change Log

Global Changes

All the blocks have been updated to the .NET 4.5 Framework.

Support for configuration by using Group Policy has been removed from this release.

Instrumentation of the blocks has been removed in this release.

The dependency on Unity has been removed from all blocks including Common. The only exception is the Policy Injection Application Block which takes a dependency on Unity.Interception.

Deprecated Blocks

The following blocks have been deprecated and removed from the Enterprise Library.

Caching Application Block
Cryptography Application Block
Security Application Block

New Blocks

Enterprise Library includes the following new blocks.

Semantic Logging Application Block
Transient Fault Handling Application Block (this block was previously a part of the Enterprise Library Integration Pack for Windows Azure)

Data Access Application Block

Exception Handling Application Block

Exception Handling Application Block objects can be created directly from configuration without using a DI container.

Logging Application Block

Rolling Behavior

The behavior of the RollingFlatFileTraceListener class has changed when the file is set to roll at midnight.
Take the following scenario:

On Monday, trace message #1 is written by the RollingFlatFileTraceListener trace listener.
On Tuesday, no trace messages are written to the log.
On Wednesday, no trace messages are written to the log.
On Thursday, trace message #2 is written by the RollingFlatFileTraceListener trace listener.

JSON Formatter

The Logging Application Block now includes a JSON formatter.

The WmiTraceListener Class

The WmiTraceListener class has been removed from this block.

Email Event Listener

Fixed several bugs that resulted in null reference exceptions being thrown when providing invalid configuration data for the email event listener.

MSMQ Event Listener

More error checking for configuration settings was added to this listener.
A new constructor was added to facilitate creating MSMQ event listener objects.

Rolling Flat File Event Listener

A new constructor was added to facilitate creating rolling flat file event listener objects.

AsynchronousTraceListenerWrapper

This new wrapper class enables you to use existing listeners to write messages asynchronously.

Semantic Logging Application Block

Transient Fault Handling Application Block

The following changes have been made to the Transient Fault Handling Application Block since it was released as part of the Enterprise Library Integration Pack for Windows Azure.

Added support for Windows Azure Caching
Added support for Windows Azure Storage 2.0
Updated to support Windows Azure Service Bus 1.8
Error code 40540 from SQL Database added as a transient error (see http://msdn.microsoft.com/en-us/library/ff394106.aspx#bkmk_throt_errors).
Added error codes 10928 and 10929 from SQL Database as transient errors (see http://blogs.msdn.com/b/psssql/archive/2012/10/31/worker-thread-governance-coming-to-azure-sql-database.aspx).
Windows Azure storage account not found is no longer treated as a transient fault.
Fixed bug whereby an attempt to load an assembly resulted in a retry on failure.
The obsolete asynchronous overloads of the RetryPolicy.ExecuteAction method have been removed. You should use the RetryPolicy.ExecuteAsync method instead.

The classes located in the namespaces in the following list can now be found in Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling:

Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.SqlAzure
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.ServiceBus
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.AzureStorage
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.Configuration
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.Cache

Policy Injection Application Block

The call handlers have been moved from the individual blocks in the Policy Injection Application Block.

Validation Application Block

The ValidationFactory class no longer automatically builds its configuration from the configuration file. You must now invoke the SetDefaultConfigurationValidatorFactory method to load the configuration from the configuration file. This is a breaking change.
The throwIfSet parameter of the SetDefaultConfigurationValidatorFactory method of the ValidationBlock has been removed. The method will not throw an exception if the configuration has already been set.

Unity

The Unity assembly is now Security Transparent.
Unity now supports NetCore (Windows Store apps).
The bug that caused a first chance exception when registering a singleton is fixed.
The bug that resulted in static properties not being filtered out when doing property injection is fixed.
Internally, the WinRT namespaces that support Unity in Windows Store apps have been renamed to NetCore.
Unity now supports resolving objects of type Lazy<T>
Unity now supports registration by convention through the new RegisterTypes method.
Unity now includes support for ASP.NET MVC and ASP.NET Web API.

Updated Wiki: EntLib6

ndelgado — Tue, 30 Apr 2013 22:06:58 GMT

Microsoft Enterprise Library 6.0 and Unity 3.0

Release to Web (RTW) - April 2013

Home page on MSDN
Official announcement
S. Somasegar's announcement
Release notes
Known issues
Change log
Official download through NuGet
Official download through the Download Center
Developer's Guide to Enterprise Library
Enterprise Library Reference Docs (Conceptual Content)
Enterprise Library Class Library (API Reference Documentation)
Developer's Guide to Unity
Unity Reference Docs (Conceptual Content)
Unity Class Library (API Reference Documentation)
Migration guide
Videos

Preview releases

Semantic Logging Application Block CTP (Feb 13, 2013)
Unity Application Block 3 CTP (Aug 13, 2012)

Other information

Updated Wiki: EntLib6

ndelgado — Tue, 30 Apr 2013 21:19:58 GMT

Microsoft Enterprise Library 6.0 and Unity 3.0

Release to Web (RTW) - April 2013

Home page on MSDN
Official announcement
S. Somasegar's announcement
Release notes
Known issues
Change log
Official download through NuGet
Official download through the Download Center
Developer's Guide to Enterprise Library
Enterprise Library Class Library (API Reference Documentation)
Developer's Guide to Unity
Unity Reference Docs (Conceptual Content)
Unity Class Library (API Reference Documentation)
Migration guide
Videos

Preview releases

Semantic Logging Application Block CTP (Feb 13, 2013)
Unity Application Block 3 CTP (Aug 13, 2012)

Other information

Updated Wiki: EntLib6

ndelgado — Tue, 30 Apr 2013 21:17:17 GMT

Microsoft Enterprise Library 6.0 and Unity 3.0

Release to Web (RTW) - April 2013

Home page on MSDN
Official announcement
S. Somasegar's announcement
Release notes
Known issues
Change log
Official download through NuGet
Official download through the Download Center
Developer's Guide
Enterprise Library Class Library (API Reference Documentation)
Developer's Guide to Unity
Unity Reference Docs (Conceptual Content)
Unity Class Library (API Reference Documentation)
Migration guide
Videos

Preview releases

Semantic Logging Application Block CTP (Feb 13, 2013)
Unity Application Block 3 CTP (Aug 13, 2012)

Other information

Updated Wiki: Home

randylevy — Fri, 26 Apr 2013 18:32:03 GMT

DOWNLOAD	Official releases	PREVIEW	Current Roadmap, Past Roadmaps
	Current release - April 2010 (5.0), Silverlight Integration Pack - May 2011, Windows Azure Integration Pack - Nov 2011, Previous releases		Enterprise Library 6.0
	Standalone Unity, Unity 2.1 - Aug 2012 Update, Unity 3.0 for .NET4.5 Preview		Follow @mspnp, @gmelnik and the #entlib hashtag
LEARN	Hands-on Labs	GET SUPPORT	Discussion Forum
	EntLib5 Developer's Guide		Issue Tracker
	Videos, Webcast Demos		Support How-to
	EntLib FAQ		Sample Projects
	Reference documentation
CONTRIBUTE	Share extensions via EntLibContrib Project (Jan 2010 Release)	PROVIDE FEEDBACK	EntLib satisfaction survey
	Hosting your extension in your own CodePlex project? Tag it with Enterprise Library		Submit suggestions
			Report bugs

News

Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library News Feed

Just released - Microsoft Enterprise Library 6

Friday, April 26, 2013 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Embracing Semantic Logging

Thursday, February 07, 2013 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Enterprise Library 6.0 - Vision/Scope

Thursday, November 08, 2012 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Enterprise Library vNext - Simplified!

Thursday, August 23, 2012 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Transient Fault Handling Application Block (Topaz) updates

Tuesday, August 21, 2012 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Announcing the Enterprise Library Integration Pack for Windows Azure with Autoscaling, Transient Fault Handling and more

Friday, December 02, 2011 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Unity 3.0 Preview for .NET 4.5

Friday, October 28, 2011 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Windows Azure Autoscaling Block BETA is out

Friday, October 14, 2011 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

WASABi scale groups

Friday, October 07, 2011 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Announcing Windows Azure Autoscaling Block preview

Monday, September 12, 2011 | From Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library

Grigori Melnik: Thoughts on Agile Software Engineering and Beyond : Enterprise Library News Feed

Software Mechanics News Feed

Entlib 5.0 Hands-on labs released

Tuesday, May 25, 2010 | From Software Mechanics

Entlib 5.0 Hands-on labs released

Tuesday, May 25, 2010 | From Software Mechanics

Unity 2.0, Entlib Docs released

Wednesday, May 05, 2010 | From Software Mechanics

Catching up with recent stuff

Sunday, May 02, 2010 | From Software Mechanics

End of an era

Saturday, April 03, 2010 | From Software Mechanics

Software Mechanics News Feed

Notes From the Team Room : Enterprise Library News Feed

Enterprise Library 5.0: Some Architecture Changes

Wednesday, June 24, 2009 | From Notes From the Team Room : Enterprise Library

Enterprise Library 5.0: Some Architecture Changes

Wednesday, June 24, 2009 | From Notes From the Team Room : Enterprise Library

Enterprise Library Needs Your Vote

Friday, March 27, 2009 | From Notes From the Team Room : Enterprise Library

Notes From the Team Room : Enterprise Library News Feed

Writing ... or Just Practicing? : Enterprise Library News Feed

Try, Try, and Try Again

Sunday, February 12, 2012 | From Writing ... or Just Practicing? : Enterprise Library

Additional Integrational Hybridization

Sunday, October 09, 2011 | From Writing ... or Just Practicing? : Enterprise Library

Hybrid Triangulation (with Cat Food and Bananas)

Monday, September 26, 2011 | From Writing ... or Just Practicing? : Enterprise Library

Time to Stop Typing and Start Thinking

Monday, September 12, 2011 | From Writing ... or Just Practicing? : Enterprise Library

It Configures

Sunday, May 09, 2010 | From Writing ... or Just Practicing? : Enterprise Library

Writing ... or Just Practicing? : Enterprise Library News Feed

patterns & practices Links

Updated Wiki: EntLib6Advisors

gmelnik — Fri, 26 Apr 2013 16:10:37 GMT

Microsoft Enterprise Library 6.0/ Unity 3.0

Advisory Board Members

Chris Tavares
Daniel Piessens
Emilio Martinez Vazquez
Kelly Sommers
Timothy Stockstill
Jon Wagner
Tom Hollander
Trent Swanson
Ercenk Keresteci
Lenny Fenster
Niu Isabel
Jeremy Likness
Andrei Marukovich
Fabian Fernandez
Scott Densmore
Bob Brumfield
Robert Vettor
Rick Rainey
Ksenia Mukhortova
Peter Nilsson
Jeremy Woo-Sam
Randy Levy
Jon Wagner
Matias Woloski
Joseph M. Blank
Deon Heyns
Nikos Baxevanis
Walter Wu
Tom Hollander
Fabian Fernandez
Bill Wilder
Michael Wood
Matthew A. Kean
Peter Ritchie
Jason Hogg
Christopher Maneu
Jared M. Shaver
Sebastian Weber
Luke Sigler
Mark Simms
Rafael Fernandez Moctezuma
Michael Thomassy
Christopher Bennage

Updated Wiki: EntLib6

gmelnik — Fri, 26 Apr 2013 13:26:49 GMT

Microsoft Enterprise Library 6.0 and Unity 3.0

Release to Web (RTW) - April 2013

Preview releases

Semantic Logging Application Block CTP (Feb 13, 2013)
Unity Application Block 3 CTP (Aug 13, 2012)

Other information

Updated Wiki: EntLib6

gmelnik — Thu, 25 Apr 2013 18:56:47 GMT

Microsoft Enterprise Library 6.0 and Unity 3.0

Release to Web (RTW) - April 2013

Preview releases

Semantic Logging Application Block CTP (Feb 13, 2013)
Unity Application Block 3 CTP (Aug 13, 2012)

Other information

Updated Wiki: EntLib6ReleaseNotes

gmelnik — Thu, 25 Apr 2013 18:55:56 GMT

Microsoft Enterprise Library 6 – Final Release

Release Notes

Where to get it?

Via NuGet – use the NuGet Package Manager in Visual Studio and search online for the “enterpriselibrary” packages. Pick the official Microsoft packages.

What’s New in this Release?

This major release of Enterprise Library contains many compelling new features and updates that will make developers more productive. These include:

Major changes throughout Enterprise Library to make it simpler and easier to learn and use whilst minimizing the impact of these changes for existing users.
A new Semantic Logging Application Block to make it easier to adopt semantic/structured logging in your applications.
The addition of the Transient Fault Handling Block as a full member of the library to help you make your on-premises and Windows Azure based applications more resilient to transient errors.
Several enhancements to Unity type registration to help you streamline the registration of types in the Unity container.
Support for Windows Store apps.
Simpler programmatic configuration for all the blocks.
Deeper integration with other technologies such as ASP.NET MVC and WebApi.

The detailed change log is included in the Enterprise Library documentation and also at the end of this document.

Installing with Previous Versions of Enterprise Library

You cannot install Enterprise Library 6 side-by-side with a previous version of the library in the same Visual Studio project.

System requirements

Supported architectures: x86 and x64.
Operating systems: Microsoft Windows® 8, Microsoft Windows® 7, Windows Server 2008 R2, Windows Server 2012.
Supported .NET Frameworks: Microsoft .NET Framework 4.5, .NET for Windows Store Apps (previously known as WinRT) for Unity and the Transient Fault Handling Application Block.
Rich development environment: Microsoft Visual Studio 2012, Professional, Ultimate, or Express editions.

For the Data Access Application Block, the following is also required:

A database server running a database that is supported by a .NET Framework 4.5 data provider.

For the Logging Application Block, the following may be required:

If you are using the Message Queuing (MSMQ) Trace Listener to store log messages, you need the Microsoft Message Queuing (MSMQ) components installed.
If you are using the Database Trace Listener to store log messages, you need access to a database server.
If you are using the E-mail Trace Listener to store log messages, you need access to an SMTP server.

For the Semantic Logging Application Block, the following may be required:

If you are using the SQL Database Sink to store log messages, you need access to a SQL Server database server. The following are supported: SQL Server 2008 and higher, SQL Server LocalDB, Windows Azure SQL Database.
If you are using the Windows Azure Sink to store log messages, you need access to a Windows Azure storage account. You must also install the Windows Azure SDK Version 1.8.

For the Transient Fault Handling Application Block, the following is required to install the NuGet package:

NuGet 2.2. This is included in Visual Studio 2012 Update 2. Once the package is downloaded, you can copy the assemblies to a machine that does not have NuGet 2.2 and use the block there.

If these dependencies are not met, you may not be able to use certain Enterprise Library features.

Learning More

The following learning resources are recommended:

Enterprise Library Reference Documentation
Unity Reference Documentation
Enterprise Library Developer’s Guide
Unity Developer’s Guide
Migration Guide
Hands-on Labs (available later)
Discussion forum

Providing feedback

Support

Community support is provided via Enterprise Library Codeplex forum.

Known Issues

If you are using the Transient Fault Handling Application Block, you should ensure that you are using version 4.0.30319.18003 or later of mscorlib.dll, otherwise you may see a VerificationException exception at run time. For more information, see http://support.microsoft.com/kb/2748646.
If you are using the Transient Fault Handling Application Block, you must have NuGet 2.2 in order to install the NuGet package. Note that this update is included in Visual Studio 2012, Update 2.
To run the coded UI tests in the Reference Implementation solutions, you must have the Visual Studio 2012 Ultimate edition.
The Semantic Logging Application Block uses the TraceEvent library (http://bcl.codeplex.com/wikipage?title=TraceEvent) internally. The Globalization Warnings reported by FxCop static analysis in this library have not been addressed.
The Semantic Logging Application Block running out-of-process only supports logging events authored using the managed EventSource class.
Using the Semantic Logging Application Block, you should not new up a listener, write a log message, and the dispose the listener. The typical usage pattern is to initialize listeners during application start up, log messages while the application is running, and then dispose the listeners during application shutdown.
The scripts included with the Semantic Logging Application Block to create a database for the SqlDatabaseSink only support SQL Server 2008 or higher, SQL Server LocalDB, Windows Azure SQL Database.
Localized event source using EventSourceAttribute.LocalizationResources when using Semantic Logging Application Block in process is not currently supported.
The Logging Application Block declarative configuration does not support runtime configuration changes.
If you are writing to the Windows Event Log using the Logging Application Block from an application that does not run with admin rights, you must ensure that you add the event source first by using the following PowerShell command:

New-EventLog -LogName Application -Source 'Enterprise Library Logging'

Documentation has not been tested for this release and the final documentation will be available later.
QuickStarts and sample code included have not been extensively tested.

Change Log

Global Changes

Deprecated Blocks

The following blocks have been deprecated and removed from the Enterprise Library.

Caching Application Block
Cryptography Application Block
Security Application Block

New Blocks

Enterprise Library includes the following new blocks.

Semantic Logging Application Block
Transient Fault Handling Application Block (this block was previously a part of the Enterprise Library Integration Pack for Windows Azure)

Data Access Application Block

Exception Handling Application Block

Exception Handling Application Block objects can be created directly from configuration without using a DI container.

Logging Application Block

Rolling Behavior

The behavior of the RollingFlatFileTraceListener class has changed when the file is set to roll at midnight.
Take the following scenario:

On Monday, trace message #1 is written by the RollingFlatFileTraceListener trace listener.
On Tuesday, no trace messages are written to the log.
On Wednesday, no trace messages are written to the log.
On Thursday, trace message #2 is written by the RollingFlatFileTraceListener trace listener.

JSON Formatter

The Logging Application Block now includes a JSON formatter.

The WmiTraceListener Class

The WmiTraceListener class has been removed from this block.

Email Event Listener

Fixed several bugs that resulted in null reference exceptions being thrown when providing invalid configuration data for the email event listener.

MSMQ Event Listener

More error checking for configuration settings was added to this listener.
A new constructor was added to facilitate creating MSMQ event listener objects.

Rolling Flat File Event Listener

A new constructor was added to facilitate creating rolling flat file event listener objects.

AsynchronousTraceListenerWrapper

This new wrapper class enables you to use existing listeners to write messages asynchronously.

Semantic Logging Application Block

Transient Fault Handling Application Block

The following changes have been made to the Transient Fault Handling Application Block since it was released as part of the Enterprise Library Integration Pack for Windows Azure.

Added support for Windows Azure Caching
Added support for Windows Azure Storage 2.0
Updated to support Windows Azure Service Bus 1.8
Error code 40540 from SQL Database added as a transient error (see http://msdn.microsoft.com/en-us/library/ff394106.aspx#bkmk_throt_errors).
Added error codes 10928 and 10929 from SQL Database as transient errors (see http://blogs.msdn.com/b/psssql/archive/2012/10/31/worker-thread-governance-coming-to-azure-sql-database.aspx).
Windows Azure storage account not found is no longer treated as a transient fault.
Fixed bug whereby an attempt to load an assembly resulted in a retry on failure.
The obsolete asynchronous overloads of the RetryPolicy.ExecuteAction method have been removed. You should use the RetryPolicy.ExecuteAsync method instead.

The classes located in the namespaces in the following list can now be found in Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling:

Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.SqlAzure
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.ServiceBus
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.AzureStorage
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.Configuration
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.Cache

Policy Injection Application Block

The call handlers have been moved from the individual blocks in the Policy Injection Application Block.

Validation Application Block

The Unity assembly is now Security Transparent.
Unity now supports NetCore (Windows Store apps).
The bug that caused a first chance exception when registering a singleton is fixed.
The bug that resulted in static properties not being filtered out when doing property injection is fixed.
Internally, the WinRT namespaces that support Unity in Windows Store apps have been renamed to NetCore.
Unity now supports resolving objects of type Lazy<T>
Unity now supports registration by convention through the new RegisterTypes method.
Unity now includes support for ASP.NET MVC and ASP.NET Web API.

Updated Wiki: EntLib6ReleaseNotes

dominicbetts — Thu, 25 Apr 2013 18:38:53 GMT

Microsoft Enterprise Library 6 – Final Release

Release Notes

Updated 4/22/2013

Welcome to the final release of Microsoft Enterprise Library 6!
This document contains a brief summary of Microsoft Enterprise Library 6, including late-breaking information that is not included in the main documentation. Additional information and bug fixes delivered after release are available on the Enterprise Library Community site and on the Enterprise Library MSDN site.

Where to get it?

Via NuGet – use the NuGet Package Manager in Visual Studio and search online for the “enterpriselibrary” packages. Pick the official Microsoft packages.

What’s New in this Release?

This major release of Enterprise Library contains many compelling new features and updates that will make developers more productive. These include:

Major changes throughout Enterprise Library to make it simpler and easier to learn and use whilst minimizing the impact of these changes for existing users.
A new Semantic Logging Application Block to make it easier to adopt semantic/structured logging in your applications.
The addition of the Transient Fault Handling Block as a full member of the library to help you make your on-premises and Windows Azure based applications more resilient to transient errors.
Several enhancements to Unity type registration to help you streamline the registration of types in the Unity container.
Support for Windows Store apps.
Simpler programmatic configuration for all the blocks.
Deeper integration with other technologies such as ASP.NET MVC and WebApi.

The detailed change log is included in the Enterprise Library documentation and also at the end of this document.

Installing with Previous Versions of Enterprise Library

You cannot install Enterprise Library 6 side-by-side with a previous version of the library in the same Visual Studio project.

System requirements

Supported architectures: x86 and x64.
Operating systems: Microsoft Windows® 8, Microsoft Windows® 7, Windows Server 2008 R2, Windows Server 2012.
Supported .NET Frameworks: Microsoft .NET Framework 4.5, .NET for Windows Store Apps (previously known as WinRT) for Unity and the Transient Fault Handling Application Block.
Rich development environment: Microsoft Visual Studio 2012, Professional, Ultimate, or Express editions.

For the Data Access Application Block, the following is also required:

A database server running a database that is supported by a .NET Framework 4.5 data provider.

For the Logging Application Block, the following may be required:

If you are using the Message Queuing (MSMQ) Trace Listener to store log messages, you need the Microsoft Message Queuing (MSMQ) components installed.
If you are using the Database Trace Listener to store log messages, you need access to a database server.
If you are using the E-mail Trace Listener to store log messages, you need access to an SMTP server.

For the Semantic Logging Application Block, the following may be required:

If you are using the SQL Database Sink to store log messages, you need access to a SQL Server database server. The following are supported: SQL Server 2008 and higher, SQL Server LocalDB, Windows Azure SQL Database.
If you are using the Windows Azure Sink to store log messages, you need access to a Windows Azure storage account. You must also install the Windows Azure SDK Version 1.8.

For the Transient Fault Handling Application Block, the following is required to install the NuGet package:

NuGet 2.2. This is included in Visual Studio 2012 Update 2. Once the package is downloaded, you can copy the assemblies to a machine that does not have NuGet 2.2 and use the block there.

If these dependencies are not met, you may not be able to use certain Enterprise Library features.

Learning More

The following learning resources are recommended:

Enterprise Library Reference Documentation
Unity Reference Documentation
Enterprise Library Developer’s Guide
Unity Developer’s Guide
Migration Guide
Hands-on Labs (available later)
Discussion forum

Providing feedback

Support

Community support is provided via Enterprise Library Codeplex forum.

Known Issues

If you are using the Transient Fault Handling Application Block, you should ensure that you are using version 4.0.30319.18003 or later of mscorlib.dll, otherwise you may see a VerificationException exception at run time. For more information, see http://support.microsoft.com/kb/2748646.
If you are using the Transient Fault Handling Application Block, you must have NuGet 2.2 in order to install the NuGet package. Note that this update is included in Visual Studio 2012, Update 2.
To run the coded UI tests in the Reference Implementation solutions, you must have the Visual Studio 2012 Ultimate edition.
The Semantic Logging Application Block uses the TraceEvent library (http://bcl.codeplex.com/wikipage?title=TraceEvent) internally. The Globalization Warnings reported by FxCop static analysis in this library have not been addressed.
The Semantic Logging Application Block running out-of-process only supports logging events authored using the managed EventSource class.
Using the Semantic Logging Application Block, you should not new up a listener, write a log message, and the dispose the listener. The typical usage pattern is to initialize listeners during application start up, log messages while the application is running, and then dispose the listeners during application shutdown.
The scripts included with the Semantic Logging Application Block to create a database for the SqlDatabaseSink only support SQL Server 2008 or higher, SQL Server LocalDB, Windows Azure SQL Database.
Localized event source using EventSourceAttribute.LocalizationResources when using Semantic Logging Application Block in process is not currently supported.
The Logging Application Block declarative configuration does not support runtime configuration changes.
If you are writing to the Windows Event Log using the Logging Application Block from an application that does not run with admin rights, you must ensure that you add the event source first by using the following PowerShell command:

New-EventLog -LogName Application -Source 'Enterprise Library Logging'

Documentation has not been tested for this release and the final documentation will be available later.
QuickStarts and sample code included have not been extensively tested.

Change Log

Global Changes

Deprecated Blocks

The following blocks have been deprecated and removed from the Enterprise Library.

Caching Application Block
Cryptography Application Block
Security Application Block

New Blocks

Enterprise Library includes the following new blocks.

Semantic Logging Application Block
Transient Fault Handling Application Block (this block was previously a part of the Enterprise Library Integration Pack for Windows Azure)

Data Access Application Block

Exception Handling Application Block

Exception Handling Application Block objects can be created directly from configuration without using a DI container.

Logging Application Block

Rolling Behavior

The behavior of the RollingFlatFileTraceListener class has changed when the file is set to roll at midnight.
Take the following scenario:

On Monday, trace message #1 is written by the RollingFlatFileTraceListener trace listener.
On Tuesday, no trace messages are written to the log.
On Wednesday, no trace messages are written to the log.
On Thursday, trace message #2 is written by the RollingFlatFileTraceListener trace listener.

JSON Formatter

The Logging Application Block now includes a JSON formatter.

The WmiTraceListener Class

The WmiTraceListener class has been removed from this block.

Email Event Listener

Fixed several bugs that resulted in null reference exceptions being thrown when providing invalid configuration data for the email event listener.

MSMQ Event Listener

More error checking for configuration settings was added to this listener.
A new constructor was added to facilitate creating MSMQ event listener objects.

Rolling Flat File Event Listener

A new constructor was added to facilitate creating rolling flat file event listener objects.

AsynchronousTraceListenerWrapper

This new wrapper class enables you to use existing listeners to write messages asynchronously.

Semantic Logging Application Block

Transient Fault Handling Application Block

The following changes have been made to the Transient Fault Handling Application Block since it was released as part of the Enterprise Library Integration Pack for Windows Azure.

Added support for Windows Azure Caching
Added support for Windows Azure Storage 2.0
Updated to support Windows Azure Service Bus 1.8
Error code 40540 from SQL Database added as a transient error (see http://msdn.microsoft.com/en-us/library/ff394106.aspx#bkmk_throt_errors).
Added error codes 10928 and 10929 from SQL Database as transient errors (see http://blogs.msdn.com/b/psssql/archive/2012/10/31/worker-thread-governance-coming-to-azure-sql-database.aspx).
Windows Azure storage account not found is no longer treated as a transient fault.
Fixed bug whereby an attempt to load an assembly resulted in a retry on failure.
The obsolete asynchronous overloads of the RetryPolicy.ExecuteAction method have been removed. You should use the RetryPolicy.ExecuteAsync method instead.

The classes located in the namespaces in the following list can now be found in Microsoft.Practices.EnterpriseLibrary.TransientFaultHandling:

Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.SqlAzure
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.ServiceBus
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.AzureStorage
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.Configuration
Microsoft.Practices.EnterpriseLibrary.WindowsAzure.TransientFaultHandling.Cache

Policy Injection Application Block

The call handlers have been moved from the individual blocks in the Policy Injection Application Block.

Validation Application Block

The Unity assembly is now Security Transparent.
Unity now supports NetCore (Windows Store apps).
The bug that caused a first chance exception when registering a singleton is fixed.
The bug that resulted in static properties not being filtered out when doing property injection is fixed.
Internally, the WinRT namespaces that support Unity in Windows Store apps have been renamed to NetCore.
Unity now supports resolving objects of type Lazy<T>
Unity now supports registration by convention through the new RegisterTypes method.
Unity now includes support for ASP.NET MVC and ASP.NET Web API.