entlib Release Rss Feed

Updated Release: Semantic Logging Application Block - CTP (Feb 12, 2013)

gmelnik — Mon, 06 May 2013 05:28:27 GMT

Semantic Logging Application Block

Comunity Technical Preview (CTP) Release

Here you will find source code, out-of-proc service, sample application and documentation for the new Semantic Logging Application Block (SLAB).

The binaries are available via NuGet.

See also:

Note: When downloading a ZIP file, remember to Unblock it first prior to extracting (Right Click and then look under Security) as it may be blocked by the OS.

Provide your feedback via the Discussions forum.

Released: Semantic Logging Application Block - CTP (Feb 12, 2013)

Mon, 06 May 2013 05:28:27 GMT

Semantic Logging Application Block

Comunity Technical Preview (CTP) Release

Here you will find source code, out-of-proc service, sample application and documentation for the new Semantic Logging Application Block (SLAB).

The binaries are available via NuGet.

See also:

Updated Release: Enterprise Library 6 - April 2013 (Apr 25, 2013)

gmelnik — Tue, 30 Apr 2013 21:55:14 GMT

Microsoft Enterprise Library 6 official binaries can be downloaded via NuGet (recommended) and from Microsoft Download Center.

Additional resources related to this release are provided here.

Note: When downloading a CHM file, remember to Unblock it (Right Click and then look under Security) as it may be blocked by the OS.

See also EntLib6 page on Codeplex.

Released: Enterprise Library 6 - April 2013 (Apr 25, 2013)

Tue, 30 Apr 2013 21:55:14 GMT

Updated Release: Enterprise Library 6 - April 2013 (Apr 25, 2013)

gmelnik — Fri, 26 Apr 2013 01:11:09 GMT

Released: Enterprise Library 6 - April 2013 (Apr 25, 2013)

Fri, 26 Apr 2013 01:11:08 GMT

Updated Release: Enterprise Library 6 - April 2013 (Doc Preview) (Apr 25, 2013)

gmelnik — Fri, 26 Apr 2013 00:30:42 GMT

Released: Enterprise Library 6 - April 2013 (Doc Preview) (Apr 25, 2013)

Fri, 26 Apr 2013 00:30:42 GMT

Updated Release: Enterprise Library 6 - April 2013 (Preview) (Apr 25, 2013)

gmelnik — Fri, 26 Apr 2013 00:26:30 GMT

Updated Release: Semantic Logging Application Block - CTP (Feb 12, 2013)

juliandominguez — Thu, 14 Feb 2013 01:15:21 GMT

Semantic Logging Application Block

Comunity Technical Preview (CTP) Release

Here you will find source code, out-of-proc service, sample application and documentation for the new Semantic Logging Application Block (SLAB).

The binaries are available via NuGet.

See also:

Released: Semantic Logging Application Block - CTP (Feb 12, 2013)

Thu, 14 Feb 2013 01:15:21 GMT

Semantic Logging Application Block

Comunity Technical Preview (CTP) Release

Here you will find source code, out-of-proc service, sample application and documentation for the new Semantic Logging Application Block (SLAB).

The binaries are available via NuGet.

See also:

Updated Release: Semantic Logging Application Block - CTP (Feb 12, 2013)

gmelnik — Thu, 14 Feb 2013 00:43:13 GMT

Semantic Logging Application Block

Comunity Technical Preview (CTP) Release

Here you will find source code, out-of-proc service, sample application and documentation for the new Semantic Logging Application Block (SLAB).

The binaries are available via NuGet.

See also:

Updated Release: EntLib Silverlight 5.0 - RTW (May 12, 2011)

gmelnik — Fri, 18 May 2012 20:20:00 GMT

The Silverlight Integration Pack can be downloaded from MSDN or via NuGet.
The Configuration console VSIX package is also available via the Visual Studio Extension Gallery.

These are additional resources.

Note: When downloading a CHM file, remember to Unblock it (Right Click and then look under Security) as it may be blocked by the OS.

Released: EntLib Silverlight 5.0 - RTW (May 12, 2011)

Fri, 18 May 2012 20:20:00 GMT

Updated Release: Integration Pack for Windows Azure - Final (Dec 01, 2011)

gmelnik — Wed, 04 Apr 2012 01:33:32 GMT

Here you will find documentation and additional resources for the final release of the Enterprise Library Integration Pack for Windows Azure, which includes the Autoscaling Application Block (Wasabi) and the Transient Fault Handling Application Block (Topaz)

The binaries and source are available via NuGet or the Download center.

See also: Windows Azure Integration Pack home page, Channel9 video walkthrough

Released: Integration Pack for Windows Azure - Final (Dec 01, 2011)

Wed, 04 Apr 2012 01:33:32 GMT

Updated Release: Integration Pack for Windows Azure - Final (Dec 01, 2011)

gmelnik — Wed, 01 Feb 2012 18:51:30 GMT

Released: Integration Pack for Windows Azure - Final (Dec 01, 2011)

Wed, 01 Feb 2012 18:51:30 GMT

Updated Release: Enterprise Library 5.0 - SQL Configuration Source (Dec 02, 2010)

gmelnik — Tue, 31 Jan 2012 23:22:10 GMT

This project contains sample code that implements an Enterprise Library configuration source that stores configuration information in a Microsoft SQL Server database. It has been tested with SQL Server 2008, but should run without changes against 2005 or 2008 R2.

What's in the Package

This project is shipped as source code. It includes Microsoft Visual Studio 2008 .sln and .csproj files, that target the .NET Framework version 3.5 SP1. The compiled binaries will work with both .NET Framework 3.5 and .NET Framework 4.0 projects. Unit and integration tests, build and deployment scripts are also included.

System Requirements

You will need to have the following tools installed on your dev machine to compile the solution:

Microsoft Visual Studio 2008 or Microsoft Visual Studio 2010
Enterprise Library 5.0

In addition, if you want to compile and run the unit tests you will need to download a copy of the Moq mock object framework from http://moq.me. The code was built against Moq version 4.0.10827. Newer versions (if any) will probably work as well. Download the Moq binaries and unzip them into the Reference Assemblies\Moq4 folder. Be sure to maintain the folder structure inside the Moq zip file.

Behavior of the Configuration Source

The SqlConfiguration source supports a subset of the features the SystemConfigurationSource and FileConfigurationSource do.

Only Enterprise Library configuration sections can be stored in the database. Other sections (for example, <appSettings>) will be stored in the physical configuration file, not the database.
The <connectionStrings> section is treated specially. The contents of <connectionStrings> will be stored both in the configuration file AND in the database. If the two sections differ, Enterprise Library Data Access Block usage will use the settings from the database, while other data access will be pulling connection strings from the file.
Hierarchical merging and redirected sections are not supported.
The design assumes that a single application's configuration is stored in the database. If you wish to have multiple applications with different configurations stored in the same database, you will need to modify the code and / or database schema.

READ THIS! Detailed Release Notes with instructions on how to customize, compile, test and deploy

Update - 1/31/2012

Additional scripts are provided to create required database objects on a SQL Azure database (see SqlConfigurationSourceforSqlAzure.zip)

Released: Enterprise Library 5.0 - SQL Configuration Source (Dec 02, 2010)

Tue, 31 Jan 2012 23:22:10 GMT

What's in the Package

System Requirements

You will need to have the following tools installed on your dev machine to compile the solution:

Microsoft Visual Studio 2008 or Microsoft Visual Studio 2010
Enterprise Library 5.0

Behavior of the Configuration Source

The SqlConfiguration source supports a subset of the features the SystemConfigurationSource and FileConfigurationSource do.

Only Enterprise Library configuration sections can be stored in the database. Other sections (for example, <appSettings>) will be stored in the physical configuration file, not the database.
The <connectionStrings> section is treated specially. The contents of <connectionStrings> will be stored both in the configuration file AND in the database. If the two sections differ, Enterprise Library Data Access Block usage will use the settings from the database, while other data access will be pulling connection strings from the file.
Hierarchical merging and redirected sections are not supported.
The design assumes that a single application's configuration is stored in the database. If you wish to have multiple applications with different configurations stored in the same database, you will need to modify the code and / or database schema.

READ THIS! Detailed Release Notes with instructions on how to customize, compile, test and deploy

Update - 1/31/2012

Additional scripts are provided to create required database objects on a SQL Azure database (see SqlConfigurationSourceforSqlAzure.zip)