entlibcontrib Wiki & Documentation Rss Feed

Updated Wiki: Home

ewdev — Thu, 01 Oct 2009 21:20:36 GMT

Welcome to the EntLib Contrib Project!

EntLib Contrib is a community-developed library of extensions to the patterns & practices Enterprise Library.

In short, if you wrote it, why not share it with the world so that they can benefit form all your hard work? With your help EntLib Contrib will evolve to include a wide range of additional providers, extensions, tools and even application blocks that can be used with Enterprise Library.

Note: Extensions in the core EntLib Contrib project should work against official builds of Enterprise Library, and should not require any modifications to the core Enterprise Library code. Contributions that involve modifications to Enterprise Library code will be considered, but any such contributions will be made available as separate releases on this site.

News!

Three new Providers for the DAAB v4.1. - In the EntLib Contribution v4.1 core upgrade you will find three new DAAB data providers for Oracle ODP.NET, IBM DB2 and MySQL. Each provider has been given a full set of Unit Tests to match those applied to the MS SQL Server data provider and, of course, a matching Northwind Database so the tests can all be consistent. Simply download the latest changeset from source code. Coming soon are two more providers, one for PostgreSQL and one for SQLite. All these providers existed in the v3.1 days but without the Unit Tests and corresponding Northwind DB. In addition these data providers have been tested with the latest versions of their respective databases and .NET Providers.

The Enterprise Library Contribution Project is to be revamped and upgraded to work from the Entlib v4.1 core - This will also include VS2008 solutions and projects and be built using .NET framework v3.5. To start the ball rolling the Resource Application Block has been upgraded to v4.1 and a new Query Application Block v4.1 has been added to provide the next level of integration for data storage. With the DAAB you got separation from the Database vendor with QAB you get separation from the data storage type with providers for the DAAB, Xml files and Web Services (documentation pending). If you are a contributor please could you contact contributor ewdev to grant permission or offer assistance to upgrade your code to v4.1 ewdev hopes to upgrade all contributions to v4.1 in the very near future and then to pave the way to supporting contributions for v5.0 when it arrives.

A new May 2009 release has been published. - This is a final round-up of all of the user contributions built around the Enterprise Library v3.1 core. Look out for the EntLib v4.1 core upgrade coming next.

What's in EntLib Contrib?

The latest release of EntLib Contrib is Enterprise Library Contrib v3.1 May 2009. It contains the following functionality. For more detailed documentation, follow the link to the release home page.

Common Block extensions
- TypeConfigurationElement<T>, AnonymousConfigurationElement
Data Access Application Block extensions
- MySql, SQLite and SqlEx providers
Exception Handling Application Block extensions
- SqlException Wrap Handler
Logging Application Block extensions
- LogParser, TimeStampParser
Policy Injection Application Block extensions
- PostSharp4EntLib
- New matching rules: And, Or and Not
- New call handlers: CursorCallHandler, OneWayCallHandler, SynchronizedCallHandler, ThreadSafeCallHandler, TransactionScopeCallHandler
Resource Application Block 3.1
- Configurable providers for Globalization and Localization
- Full application block complete with support for the console, instrumentation and group policies
Validation Application Block extensions
- New validators: CollectionCountValidator, CompositeRulesetValidator, TypeValidator<T>, ObjectValidator<T>, EnumDefinedValidator
- Designtime enhancements: Lightweight type picker, Test command
- Other extensions: Default validators, Argument Validation, ExternallyConfigurableObjectValidator

Other separate releases hosted on this site are:

Standalone Validation Application Block 1.2: adds deep WPF automatic object validating data-binding via a new ValidationBinding markup extension.
Extended SQL Data Access Block 3.1.1: Now integrated into the main EntLibContrib release.

Other contributions in the source code but not in the latest release:

Query Application Block 4.1 New - Next level of integration up from the DAAB providing a common interface for data stored in a DB, XML file or Web/WCF service
Resource Application Block 4.1 New - Upgraded to include Unity integration and to work with EntLib4.1 core and VS2008
The Application Block Software Factory (needs GAX)
The Strong-Naming Guidance Package (needs GAX)

Contributing to EntLib Contrib

Would you like to join as a developer of the EntLib Contrib project to share your own extensions or improve the existing codebase? Great! Here is what you need to know

Other p&p Contrib Projects

New Comment on "ASP.NET Resource Provider Model"

orovia — Thu, 13 Aug 2009 10:41:01 GMT

A easy to understand concept. But,I cannot get database resource provider work with asp.net, If I follow the method in this article I get lots of this error "The 'CodeFile' attribute cannot be used without an 'Inherits' attribute." I think the line <globalization culture="auto" uiCulture ="auto" resourceProviderFactoryType="EntLibContrib.Resource.Web.WebResourceProviderFactory, EntLibContrib.Resource" /> in the web.config as something to do with this error. Is there any working example on database resource provider for asp.net localresources

New Comment on "ASP.NET Resource Provider Model"

orovia — Wed, 12 Aug 2009 13:19:35 GMT

I cannot get database resource provide work with asp.net, If I have this line <globalization culture="auto" uiCulture ="auto" resourceProviderFactoryType="EntLibContrib.Resource.Web.WebResourceProviderFactory, EntLibContrib.Resource" /> in the web.config, I get a series of complier errors. Is there any article in internet that shows how to setup database resource provider for asp.net localresources

New Comment on "Resource Application Block 3.1"

tonyeka — Tue, 21 Jul 2009 17:00:14 GMT

Hi there, just wondering whether there will be any attempt to have a WPF sample using this block?

Updated Wiki: Home

ewdev — Tue, 05 May 2009 19:25:24 GMT

Welcome to the EntLib Contrib Project!

News!

A new May 2009 release has been published. - This is a final round-up of all of the user contributions built around the Enterprise Library v3.1 core. Look out for the EntLib v4.1 core upgrade coming next.

The Enterprise Library Contribution Project is to be revamped and upgraded to work from the Entlib v4.1 core - This will also include VS2008 solutions and projects and be built using .NET framework v3.5. To start the ball rolling the Resource Application Block has been upgraded to v4.1 and a new Query Application Block v4.1 has been added to provide the next level of integration for data storage. With the DAAB you got separation from the Database vendor with QAB you get separation from the data storage type with providers for the DAAB, Xml files and Web Services (documentation pending). If you are a contributor please could you contact contributor ewdev to grant permission or offer assistance to upgrade your code to v4.1 ewdev hopes to upgrade all contributions to v4.1 in the very near future and then to pave the way to supporting contributions for v5.0 when it arrives.

What's in EntLib Contrib?

The latest release of EntLib Contrib is Enterprise Library Contrib v3.1 May 2009. It contains the following functionality. For more detailed documentation, follow the link to the release home page.

Common Block extensions
- TypeConfigurationElement<T>, AnonymousConfigurationElement
Data Access Application Block extensions
- MySql, SQLite and SqlEx providers
Exception Handling Application Block extensions
- SqlException Wrap Handler
Logging Application Block extensions
- LogParser, TimeStampParser
Policy Injection Application Block extensions
- PostSharp4EntLib
- New matching rules: And, Or and Not
- New call handlers: CursorCallHandler, OneWayCallHandler, SynchronizedCallHandler, ThreadSafeCallHandler, TransactionScopeCallHandler
Resource Application Block 3.1
- Configurable providers for Globalization and Localization
- Full application block complete with support for the console, instrumentation and group policies
Validation Application Block extensions
- New validators: CollectionCountValidator, CompositeRulesetValidator, TypeValidator<T>, ObjectValidator<T>, EnumDefinedValidator
- Designtime enhancements: Lightweight type picker, Test command
- Other extensions: Default validators, Argument Validation, ExternallyConfigurableObjectValidator

Other separate releases hosted on this site are:

Standalone Validation Application Block 1.2: adds deep WPF automatic object validating data-binding via a new ValidationBinding markup extension.
Extended SQL Data Access Block 3.1.1: Now integrated into the main EntLibContrib release.

Other contributions in the source code but not in the latest release:

Query Application Block 4.1 New - Next level of integration up from the DAAB providing a common interface for data stored in a DB, XML file or Web/WCF service
Resource Application Block 4.1 New - Upgraded to include Unity integration and to work with EntLib4.1 core and VS2008
The Application Block Software Factory (needs GAX)
The Strong-Naming Guidance Package (needs GAX)

Contributing to EntLib Contrib

Would you like to join as a developer of the EntLib Contrib project to share your own extensions or improve the existing codebase? Great! Here is what you need to know

Other p&p Contrib Projects

Updated Wiki: Home

ewdev — Tue, 05 May 2009 18:41:18 GMT

Welcome to the EntLib Contrib Project!

News!

A new May 2009 release has been published. - This is a final round-up of all of the user contributions built around the Enterprise Library v3.1 core. Look out for the EntLib v4.1 core upgrade coming next.

The Enterprise Library Contribution Project is to be revamped and upgraded to work from the Entlib v4.1 core - This will also include VS2008 solutions and projects and be built using .NET framework v3.5. To start the ball rolling the Resource Application Block has been upgraded to v4.1 and a new Query Application Block v4.1 has been added to provide the next level of integration for data storage. With the DAAB you got separation from the Database vendor with QAB you get separation from the data storage type with providers for the DAAB, Xml files and Web Services (documentation pending). If you are a contributor please could you contact contributor ewdev to grant permission or offer assistance to upgrade your code to v4.1 ewdev hopes to upgrade all contributions to v4.1 in the very near future and then to pave the way to supporting contributions for v5.0 when it arrives.

What's in EntLib Contrib?

The latest release of EntLib Contrib is Enterprise Library Contrib v3.1 May 2009. It contains the following functionality. For more detailed documentation, follow the link to the release home page.

Common Block extensions
- TypeConfigurationElement<T>, AnonymousConfigurationElement
Data Access Application Block extensions
- MySql, SQLite and SqlEx providers
Exception Handling Application Block extensions
- SqlException Wrap Handler
Logging Application Block extensions
- LogParser, TimeStampParser
Policy Injection Application Block extensions
- PostSharp4EntLib
- New matching rules: And, Or and Not
- New call handlers: CursorCallHandler, OneWayCallHandler, SynchronizedCallHandler, ThreadSafeCallHandler, TransactionScopeCallHandler
Resource Application Block 3.1
- Configurable providers for Globalization and Localization
Validation Application Block extensions
- New validators: CollectionCountValidator, CompositeRulesetValidator, TypeValidator<T>, ObjectValidator<T>, EnumDefinedValidator
- Designtime enhancements: Lightweight type picker, Test command
- Other extensions: Default validators, Argument Validation, ExternallyConfigurableObjectValidator

Other separate releases hosted on this site are:

Standalone Validation Application Block 1.2: adds deep WPF automatic object validating data-binding via a new ValidationBinding markup extension.
Extended SQL Data Access Block 3.1.1: Now integrated into the main EntLibContrib release.

Other contributions in the source code but not in the latest release:

Query Application Block 4.1 New - Next level of integration up from the DAAB providing a common interface for data stored in a DB, XML file or Web/WCF service
Resource Application Block 4.1 New - Upgraded to include Unity integration and to work with EntLib4.1 core and VS2008
The Application Block Software Factory (needs GAX)
The Strong-Naming Guidance Package (needs GAX)

Contributing to EntLib Contrib

Would you like to join as a developer of the EntLib Contrib project to share your own extensions or improve the existing codebase? Great! Here is what you need to know

Other p&p Contrib Projects

Updated Wiki: Home

ewdev — Tue, 05 May 2009 18:20:27 GMT

Welcome to the EntLib Contrib Project!

News!

A new May 2009 release has been published. - This is a final round-up of all of the user contributions built around the Enterprise Library v3.1 core. look for the EntLib v4.1 core upgrade coming next.

The Enterprise Library Contribution Project is to be revamped and upgraded to work from the Entlib v4.1 core - This will also include VS2008 solutions and projects and be built using .NET framework v3.5. To start the ball rolling the Resource Application Block has been upgraded to v4.1 and a new Query Application Block v4.1 has been added to provide the next level of integration for data storage. With the DAAB you got separation from the Database vendor with QAB you get separation from the data storage type with providers for the DAAB, Xml files and Web Services (documentation pending). If you are a contributor please could you contact contributor ewdev to grant permission or offer assistance to upgrade your code to v4.1 ewdev hopes to upgrade all contributions to v4.1 in the very near future and then to pave the way to supporting contributions for v5.0 when it arrives.

What's in EntLib Contrib?

The latest release of EntLib Contrib is Enterprise Library Contrib v3.1 May 2009. It contains the following functionality. For more detailed documentation, follow the link to the release home page.

Common Block extensions
- TypeConfigurationElement<T>, AnonymousConfigurationElement
Data Access Application Block extensions
- MySql, SQLite and SqlEx providers
Exception Handling Application Block extensions
- SqlException Wrap Handler
Logging Application Block extensions
- LogParser, TimeStampParser
Policy Injection Application Block extensions
- PostSharp4EntLib
- New matching rules: And, Or and Not
- New call handlers: CursorCallHandler, OneWayCallHandler, SynchronizedCallHandler, ThreadSafeCallHandler, TransactionScopeCallHandler
Resource Application Block 3.1
- Configurable providers for Globalization and Localization
Validation Application Block extensions
- New validators: CollectionCountValidator, CompositeRulesetValidator, TypeValidator<T>, ObjectValidator<T>, EnumDefinedValidator
- Designtime enhancements: Lightweight type picker, Test command
- Other extensions: Default validators, Argument Validation, ExternallyConfigurableObjectValidator

Other separate releases hosted on this site are:

Standalone Validation Application Block 1.2: adds deep WPF automatic object validating data-binding via a new ValidationBinding markup extension.
Extended SQL Data Access Block 3.1.1: Now integrated into the main EntLibContrib release.

Other contributions in the source code but not in the latest release:

Query Application Block 4.1 New - Next level of integration up from the DAAB providing a common interface for data stored in a DB, XML file or Web/WCF service
Resource Application Block 4.1 New - Upgraded to include Unity integration and to work with EntLib4.1 core and VS2008
The Application Block Software Factory (needs GAX)
The Strong-Naming Guidance Package (needs GAX)

Contributing to EntLib Contrib

Would you like to join as a developer of the EntLib Contrib project to share your own extensions or improve the existing codebase? Great! Here is what you need to know

Other p&p Contrib Projects

Updated Wiki: Home

ewdev — Tue, 05 May 2009 18:16:44 GMT

Welcome to the EntLib Contrib Project!

News!

A new May 2009 release has been published. - This is a final round-up of all of the user contributions built around the Enterprise Library v3.1 core. look for the EntLib v4.1 core upgrade coming next.

The Enterprise Library Contribution Project is to be revamped and upgraded to work from the Entlib v4.1 core - This will also include VS2008 solutions and projects and be built using .NET framework v3.5. To start the ball rolling the Resource Application Block has been upgraded to v4.1 and a new Query Application Block v4.1 has been added to provide the next level of integration for data storage. With the DAAB you got separation from the Database vendor with QAB you get separation from the data storage type with providers for the DAAB, Xml files and Web Services (documentation pending). If you are a contributor please could you contact contributor ewdev to grant permission or offer assistance to upgrade your code to v4.1 ewdev hopes to upgrade all contributions to v4.1 in the very near future and then to pave the way to supporting contributions for v5.0 when it arrives.

What's in EntLib Contrib?

The latest release of EntLib Contrib is Enterprise Library Contrib v3.1 May 2009. It contains the following functionality. For more detailed documentation, follow the link to the release home page.

Common Block extensions
- TypeConfigurationElement<T>, AnonymousConfigurationElement
Data Access Application Block extensions
- MySql, SQLite and SqlEx providers
Exception Handling Application Block extensions
- SqlException Wrap Handler
Logging Application Block extensions
- LogParser, TimeStampParser
Policy Injection Application Block extensions
- PostSharp4EntLib
- New matching rules: And, Or and Not
- New call handlers: CursorCallHandler, OneWayCallHandler, SynchronizedCallHandler, ThreadSafeCallHandler, TransactionScopeCallHandler
Resource Application Block 3.1
- Configurable providers for Globalization and Localization
Validation Application Block extensions
- New validators: CollectionCountValidator, CompositeRulesetValidator, TypeValidator<T>, ObjectValidator<T>, EnumDefinedValidator
- Designtime enhancements: Lightweight type picker, Test command
- Other extensions: Default validators, Argument Validation, ExternallyConfigurableObjectValidator

Other separate releases hosted on this site are:

Standalone Validation Application Block 1.2: adds deep WPF automatic object validating data-binding via a new ValidationBinding markup extension.
Extended SQL Data Access Block 3.1.1

Other contributions in the source code but not in the latest release:

Query Application Block 4.1 New - Next level of integration up from the DAAB providing a common interface for data stored in a DB, XML file or Web/WCF service
Resource Application Block 4.1 New - Upgraded to include Unity integration and to work with EntLib4.1 core and VS2008
The Application Block Software Factory (needs GAX)
The Strong-Naming Guidance Package (needs GAX)

Contributing to EntLib Contrib

Would you like to join as a developer of the EntLib Contrib project to share your own extensions or improve the existing codebase? Great! Here is what you need to know

Other p&p Contrib Projects

Updated Wiki: Home

ewdev — Tue, 05 May 2009 18:09:21 GMT

Welcome to the EntLib Contrib Project!

News!

A new May 2009 release has been published. - This is a final round-up of all of the user contributions built around the Enterprise Library v3.1 core. look for the EntLib v4.1 core upgrade coming next.

The Enterprise Library Contribution Project is to be revamped and upgraded to work from the Entlib v4.1 core - This will also include VS2008 solutions and projects and be built using .NET framework v3.5. To start the ball rolling the Resource Application Block has been upgraded to v4.1 and a new Query Application Block v4.1 has been added to provide the next level of integration for data storage. With the DAAB you got separation from the Database vendor with QAB you get separation from the data storage type with providers for the DAAB, Xml files and Web Services (documentation pending).

If you are a contributor please could you contact contributor ewdev to grant permission or offer assistance to upgrade your code to v4.1
ewdev hopes to upgrade all contributions to v4.1 in the very near future and then to pave the way to supporting contributions for v5.0 when it arrives.

What's in EntLib Contrib?

The latest release of EntLib Contrib is Enterprise Library Contrib v3.1 May 2009. It contains the following functionality. For more detailed documentation, follow the link to the release home page.

Common Block extensions
- New TypeCommandElement
Data Access Application Block extensions
- MySql, SqLite and SqlEx providers
Exception Handling Application Block extensions
- SqlException Wrap Handler
Logging Application Block extensions
- LogParser
Policy Injection Application Block extensions
- PostSharp4EntLib
- New matching rules: And, Or and Not
- New call handlers: CursorCallHandler, OneWayCallHandler, SynchronizedCallHandler, ThreadSafeCallHandler, TransactionScopeCallHandler
Validation Application Block extensions
- New validators: CollectionCountValidator, TypeValidator<T>, ObjectValidator<T>, EnumDefinedValidator
- Designtime enhancements: Lightweight type picker, Test command
- Other extensions: Default validators, Argument Validation, ExternallyConfigurableObjectValidator

Other separate releases hosted on this site are:

Standalone Validation Application Block 1.2: adds deep WPF automatic object validating data-binding via a new ValidationBinding markup extension.
Extended SQL Data Access Block 3.1.1

Other contributions in the source code but not in the latest release:

Query Application Block 4.1 New - Next level of integration up from the DAAB providing a common interface for data stored in a DB, XML file or Web/WCF service
Resource Application Block 4.1 New - Upgraded to include Unity integration and to work with EntLib4.1 core and VS2008
Resource Application Block 3.1 - Configurable providers for Globalization and Localization
The Application Block Software Factory (needs GAX)
The Strong-Naming Guidance Package (needs GAX)

Contributing to EntLib Contrib

Would you like to join as a developer of the EntLib Contrib project to share your own extensions or improve the existing codebase? Great! Here is what you need to know

Other p&p Contrib Projects

Updated Wiki: Home

ewdev — Tue, 05 May 2009 18:06:14 GMT

Welcome to the EntLib Contrib Project!

News!

A new May 2009 release has been published. - This is a final round-up of all of the user contributions built around the Enterprise Library v3.1 core. look for the EntLib v4.1 core upgrade coming next.

The Enterprise Library Contribution Project is to be revamped and upgraded to work from the Entlib v4.1 core - with VS2008 solutions and projects and .NET framework v3.5. To start the ball rolling the Resource Application Block has been upgraded to v4.1 and a new Query Application Block v4.1 has been added to provide the next level of integration for data storage. With the DAAB you got separation from the Database vendor with QAB you get separation from the data storage type with providers for the DAAB, Xml files and Web Services (documentation pending).
If you are a contributor please could you contact contributor ewdev to grant permission or offer assistance to upgrade your code to v4.1
ewdev hopes to upgrade all contributions to v4.1 in the very near future and then to pave the way to supporting contributions for v5.0 when it arrives.

What's in EntLib Contrib?

The latest release of EntLib Contrib is Enterprise Library Contrib September 2007. It contains the following functionality. For more detailed documentation, follow the link to the release home page.

Common Block extensions
- New TypeCommandElement
Data Access Application Block extensions
- MySql, SqLite and SqlEx providers
Exception Handling Application Block extensions
- SqlException Wrap Handler
Logging Application Block extensions
- LogParser
Policy Injection Application Block extensions
- PostSharp4EntLib
- New matching rules: And, Or and Not
- New call handlers: CursorCallHandler, OneWayCallHandler, SynchronizedCallHandler, ThreadSafeCallHandler, TransactionScopeCallHandler
Validation Application Block extensions
- New validators: CollectionCountValidator, TypeValidator<T>, ObjectValidator<T>, EnumDefinedValidator
- Designtime enhancements: Lightweight type picker, Test command
- Other extensions: Default validators, Argument Validation, ExternallyConfigurableObjectValidator

Other separate releases hosted on this site are:

Standalone Validation Application Block 1.2: adds deep WPF automatic object validating data-binding via a new ValidationBinding markup extension.
Extended SQL Data Access Block 3.1.1

Other contributions in the source code but not in the latest release:

Query Application Block 4.1 New - Next level of integration up from the DAAB providing a common interface for data stored in a DB, XML file or Web/WCF service
Resource Application Block 4.1 New - Upgraded to include Unity integration and to work with EntLib4.1 core and VS2008
Resource Application Block 3.1 - Configurable providers for Globalization and Localization
The Application Block Software Factory (needs GAX)
The Strong-Naming Guidance Package (needs GAX)

Contributing to EntLib Contrib

Would you like to join as a developer of the EntLib Contrib project to share your own extensions or improve the existing codebase? Great! Here is what you need to know

Other p&p Contrib Projects

Updated Wiki: Home

ewdev — Tue, 21 Apr 2009 22:28:27 GMT

Welcome to the EntLib Contrib Project!

Breaking News!

The Enterprise Library Contribution Project is to be revamped and upgraded to work from the Entlib v4.1 core with VS2008 solutions and projects and .NET framework v3.5. To start the ball rolling the Resource Application Block has been upgraded to v4.1 and a new Query Application Block v4.1 has been added to provide the next level of integration for data storage. With the DAAB you got separation from the Database vendor with QAB you get separation from the data storage type with providers for the DAAB, Xml files and Web Services (documentation pending).
If you are a contributor please could you contact contributor ewdev to grant permission or offer assistance to upgrade your code to v4.1
ewdev hopes to upgrade all contributions to v4.1 in the very near future and then to pave the way to supporting contributions for v5.0 when it arrives.

What's in EntLib Contrib?

The latest release of EntLib Contrib is Enterprise Library Contrib September 2007. It contains the following functionality. For more detailed documentation, follow the link to the release home page.

Data Access Application Block extensions
- MySql, SqLite and SqlEx providers
Exception Handling Application Block extensions
- SqlException Wrap Handler
Logging Application Block extensions
- LogParser
Policy Injection Application Block extensions
- PostSharp4EntLib
- New matching rules: And, Or and Not
- New call handlers: CursorCallHandler, OneWayCallHandler, SynchronizedCallHandler, ThreadSafeCallHandler, TransactionScopeCallHandler
Validation Application Block extensions
- New validators: CollectionCountValidator, TypeValidator<T>, ObjectValidator<T>, EnumDefinedValidator
- Designtime enhancements: Lightweight type picker, Test command
- Other extensions: Default validators, Argument Validation, ExternallyConfigurableObjectValidator

Other separate releases hosted on this site are:

Standalone Validation Application Block 1.2: adds deep WPF automatic object validating data-binding via a new ValidationBinding markup extension.
Extended SQL Data Access Block 3.1.1

Other contributions in the source code but not in the latest release:

Query Application Block 4.1 New - Next level of integration up from the DAAB providing a common interface for data stored in a DB, XML file or Web/WCF service
Resource Application Block 4.1 New - Upgraded to include Unity integration and to work with EntLib4.1 core and VS2008
Resource Application Block 3.1 - Configurable providers for Globalization and Localization
The Application Block Software Factory (needs GAX)
The Strong-Naming Guidance Package (needs GAX)

Contributing to EntLib Contrib

Would you like to join as a developer of the EntLib Contrib project to share your own extensions or improve the existing codebase? Great! Here is what you need to know

Other p&p Contrib Projects

Updated Wiki: Home

ewdev — Tue, 21 Apr 2009 22:20:58 GMT

Welcome to the EntLib Contrib project!

Breaking News!

The Enterprise Library Contribution Project is to be revamped and upgraded to work from the Entlib v4.1 core with VS2008 solutions and projects and .NET framework v3.5. To start the ball rolling the Resource Application Block has been upgraded to v4.1 and a new Query Application Block v4.1 has been added (documentation pending).
If you are a contributor please could you contact contributor ewdev to grant permission or offer assistance to upgrade your code to v4.1
ewdev hopes to upgrade all contributions to v4.1 in the very near future and then to pave the way to supporting contributions for v5.0 when it arrives.

What's in EntLib Contrib?

The latest release of EntLib Contrib is Enterprise Library Contrib September 2007. It contains the following functionality. For more detailed documentation, follow the link to the release home page.

Data Access Application Block extensions
- MySql, SqLite and SqlEx providers
Exception Handling Application Block extensions
- SqlException Wrap Handler
Logging Application Block extensions
- LogParser
Policy Injection Application Block extensions
- PostSharp4EntLib
- New matching rules: And, Or and Not
- New call handlers: CursorCallHandler, OneWayCallHandler, SynchronizedCallHandler, ThreadSafeCallHandler, TransactionScopeCallHandler
Validation Application Block extensions
- New validators: CollectionCountValidator, TypeValidator<T>, ObjectValidator<T>, EnumDefinedValidator
- Designtime enhancements: Lightweight type picker, Test command
- Other extensions: Default validators, Argument Validation, ExternallyConfigurableObjectValidator

Other separate releases hosted on this site are:

Standalone Validation Application Block 1.2: adds deep WPF automatic object validating data-binding via a new ValidationBinding markup extension.
Extended SQL Data Access Block 3.1.1

Other contributions in the source code but not in the latest release:

Query Application Block 4.1 New - Next level of integration up from the DAAB providing a common interface for data stored in a DB, XML file or Web/WCF service
Resource Application Block 4.1 New - Upgraded to include unity integration and to work with EntLib4.1 core and VS2008
Resource Application Block 3.1 - Configurable providers for Globalization and Localization
The Application Block Software Factory (needs GAX)
The Strong-Naming Guidance Package (needs GAX)

Contributing to EntLib Contrib

Would you like to join as a developer of the EntLib Contrib project to share your own extensions or improve the existing codebase? Great! Here is what you need to know

Other p&p Contrib Projects

New Comment on "SqlException Wrap Handler"

ncoimbra — Fri, 13 Feb 2009 13:31:49 GMT

Hi! I'm having trouble using this. As soon as I copy the .Design.dll assemblies to the bin folder of the EntLib, the Configuration Tool stops working properly... Any thoughts?

Updated Wiki: Home

ewdev — Tue, 23 Dec 2008 16:36:07 GMT

Welcome to the EntLib Contrib project!

What's in EntLib Contrib?

The latest release of EntLib Contrib is Enterprise Library Contrib September 2007. It contains the following functionality. For more detailed documentation, follow the link to the release home page.

Data Access Application Block extensions

MySql, SqLite and SqlEx providers

Exception Handling Application Block extensions

SqlException Wrap Handler

Logging Application Block extensions

LogParser

Policy Injection Application Block extensions

PostSharp4EntLib
New matching rules: And, Or and Not
New call handlers: CursorCallHandler, OneWayCallHandler, SynchronizedCallHandler, ThreadSafeCallHandler, TransactionScopeCallHandler

Validation Application Block extensions

New validators: CollectionCountValidator, TypeValidator<T>, ObjectValidator<T>, EnumDefinedValidator
Designtime enhancements: Lightweight type picker, Test command
Other extensions: Default validators, Argument Validation, ExternallyConfigurableObjectValidator

Other separate releases hosted on this site are:

Standalone Validation Application Block 1.2: adds deep WPF automatic object validating data-binding via a new ValidationBinding markup extension.
Extended SQL Data Access Block 3.1.1

Other contributions in the source code but not in the latest release:

Resource Application Block 3.1
The Application Block Software Factory (needs GAX)
The Strong-Naming Guidance Package (needs GAX)

Contributing to EntLib Contrib

Would you like to join as a developer of the EntLib Contrib project to share your own extensions or improve the existing codebase? Great! Here is what you need to know

Other p&p Contrib Projects

UPDATED WIKI: Home

dcazzulino — Thu, 24 Apr 2008 15:53:01 GMT

Welcome to the EntLib Contrib project!

What's in EntLib Contrib?

The latest release of EntLib Contrib is Enterprise Library Contrib September 2007. It contains the following functionality. For more detailed documentation, follow the link to the release home page.

Data Access Application Block extensions

MySql, SqLite and SqlEx providers

Exception Handling Application Block extensions

SqlException Wrap Handler

Logging Application Block extensions

LogParser

Policy Injection Application Block extensions

PostSharp4EntLib
New matching rules: And, Or and Not
New call handlers: CursorCallHandler, OneWayCallHandler, SynchronizedCallHandler, ThreadSafeCallHandler, TransactionScopeCallHandler

Validation Application Block extensions

New validators: CollectionCountValidator, TypeValidator<T>, ObjectValidator<T>, EnumDefinedValidator
Designtime enhancements: Lightweight type picker, Test command
Other extensions: Default validators, Argument Validation, ExternallyConfigurableObjectValidator

Other separate releases hosted on this site are:

Standalone Validation Application Block 1.2: adds deep WPF automatic object validating data-binding via a new ValidationBinding markup extension.
Extended SQL Data Access Block 3.1.1

New contributions coming soon:

Resource Application Block 3.1

Contributing to EntLib Contrib

Would you like to join as a developer of the EntLib Contrib project to share your own extensions or improve the existing codebase? Great! Here is what you need to know

Other p&p Contrib Projects

UPDATED WIKI: About p&p "Contrib" projects

gblock — Tue, 15 Apr 2008 14:41:43 GMT

About p&p Contrib Projects

p&p "Contrib" projects are community-developed and -managed projects that extend patterns & pratices deliverables with new and useful functionality. Currently, the following p&p Contrib projects are live:

Contrib projects are of two types:

Extensions - extend the functionality in the core patterns & practices deliverable by levaraging built-in extensibility points. They do not modify or fork the original deliverable.
Forks - contain modifications to the guidance packages and/or application blocks. These may also include extensions.

While core patterns & practices deliverables are developed by Microsoft and its vendors, anyone in the community may contribute to a p&p Contrib project, subject to processes and standards determined by the community team.

FAQ

Q: Why has the patterns & practices team set up "Contrib" projects?
A: The p&p Contrib projects were started to make it easier for community members to extend the value of p&p deliverables, without needing to wait for the p&p team to implement good ideas in official releases. While it has always been possible for community members to create and share extensions / forks to p&p deliverables, the Contrib projects are intended to provide a "center of gravity" to encourage easier sharing and discovery of useful code. Additionally through contrib the community can establish a set of standards for such projects thereby resulting in a clear set of expectations and more uniform experience for users of the contrib projects.

Q: I have built an extension to a p&p deliverable. Why would I want to contribute it to a p&p Contrib project?
A: Obviously it's up to you to decide if and how to share code you have developed. The big advantage of sharing code through a Contrib project is that it will be exposed to a lot of people without you needing to do your own promotion. It also offers a benefit to users, as they can go to one location to find a variety of useful extensions, rather than having to find many different deliverables from different sites with different licenses. On the other hand, contributing to a p&p Contrib project will give you limited control over the license, positioning and the evolution of the code, since these will be decided by a team of community developers.

Q: Is anyone allowed to contribute to a p&p Contrib project?
A: Anyone who has created an extension to a p&p deliverable is encoraged to contribute to the relevant p&p Contrib project. However in order to maintain the desired level of quality, each project team may have its own standards and requirements for developers who wish to join the team. These requirements will be decided by project team, and wil not be dictated by Microsoft. Anyone interested in contributing to a project should contact one of the project coordinators, as listed on the People tab in CodePlex.

Q: Who gets to be a "coordinator"?
A: Project coordinators are responsible for deciding who gets to check in, establishing and enforcing processes and guidelines, and ensuring the codebase remains at a suitable quality. Initially this role will be played by p&p members, but our plan is to transition this role to one or more external community members over time. If you believe you are qualified for this role and are able to dedictate the necessary amount of time, please contact an existing coordinator to discuss this further.

Q: What license will apply to code I contribute to a p&p Contrib project?
A: Any code you contribute to a p&p Contrib project will be distributed under that project's license (typically, the Microsoft Permissive License).

Q: Will code in p&p Contrib projects ever make its way into core p&p deliverables such as Enterprise Library?
A: This is not the primary intent of Contrib projects. In general you should expect that extensions in Contrib projects will remain separate from the core p&p deliverables. If there are any contributions that both the community and the p&p team agree should become part of the core deliverable, Microsoft may investigate options for licensing the code; however this is unlikely to be a common scenario.

Q: Can I trust code in a p&p Contrib project?
A: As with other open source and patterns & practices projects, the Contrib projects come with no warranties or guarantees, and it is up to the user to decide how much they trust the code. Ultimately the quality of the code and the processes around testing and consistency will be governed by the community.

UPDATED WIKI: Resource Application Block 3.1

ewdev — Fri, 11 Apr 2008 16:11:31 GMT

Resource Application Block 3.1

The Resource Application Block is all about resource management, localization and globalization. The Resource Application Block gives developers a provider model to get to resources from a variety of different sources and source types using the features of the Enterprise Library 3.1. All configuration of those resources naturally uses the Enterprise Library Configuration Console.

The developer is not limited to the providers out-of-the-box but can extend the block by adding providers of their own in the normal Enterprise Library extensible fashion.

Main Features

The following are the main features associated with the Resource Application Block:

Greater flexibility to choose how you host your resources. With the Resource Application Block you can now choose whether to centralise or distribute resources, whether to leave resources in editable files rather than embed into assemblies, pull in resources from other projects and thus treat resources like reusable modules as per the Object Oriented paradigm,
You can use either the stand-alone Enterprise Library Configuration Console or the Visual Studio integrated Console to manage all Resource Application Block settings.
You have a choice of resource providers to manage resources from a variety of sources such as assembly embedded resources, xml resources (.resx files), binary resources (.resources files) and database resources (any DB you can get to from the Data Access Application Block).
If you need to manage resources from a source type not currently supported then you can extend the application block by creating custom resource providers
You can generate strongly typed resource classes for any resource provider type directly from the Enterprise Library Configuration Console in either C# or VB.
A web resource provider is included to enable the developer to use the Resource Application Block with the localization features provided within ASP.NET. This works for both local and global resources.
All Resource Application Block managers are based on an extended ComponentResourceManager to enable reflection-style resource assignments to be made to Windows Forms component properties using the ApplyResources method within the ExtendedComponentResourceManager. Unfortunately, owing to the current closed nature of the Windows Forms designer CodeDomProvider model, with respect to localization, it has not been possible to extend the full Windows Forms localization feature, however see Windows Forms Designer for what you can do with the ExtendedComponentResourceManager.
A resource provider presents the developer with an appropriate resource manager type. Each resource manager supported within the Resource Application Block is provided with a corresponding resource writer to enable editing of the various resource storage types using any IResourceWriter enabled resource editor. These resource writers also support the extended data node interface allowing for comments, file references and custom types to be stored (except for binary resource files that do not support comments).
Management and monitoring features include Windows Active Directory Group Policy integration and instrumentation features such as Performance Counters, Windows EventLog logging and WMI events.

Key Uses

If you need convincing as to why you would use this block, have a look at the following reasons:

You need to localize your application. The Resource Application Block gives you way more choices for managing localization than with standard means.
You have a large number of resources spread between many files. The standard approach is to hold a set of resources for each assembly of an application. If you have a large number of assemblies in your application and you are supporting several different cultures then the number of resource files can be considerable, managing these files and managing translators and translations etc becomes a complex operation. You can use the Resource Application Block to centralise those resources or at least break them down into a manageable set. The database provider is an ideal choice when things start to get out of hand.
You think you might need to manage some of your resources on-the-fly without having to re-compile and re-install assemblies each time. The Resource Application Block can provide resources directly from source files (e.g. .resx or .resources files) and does not hold those files open once read. This allows for on-the-fly changes to resource values e.g. spelling corrections, word replacement, change of colour etc.
You may need to change from assembly embedded resources to a database as an application scales up. Because all resource storage types are managed through configuration it makes it very easy to swap from one storage type to another.

A Quick Code Sample

The following code sample shows the basic function of the block, how to get the default resource manager and use its resources. Note that an indexer is used, based on a string key and an optional type (string is the default) to get at the resources. The standard GetString(), GetObject() and GetStream() methods are still available however:

[C#]

// get the default resource manager. Note: this is an EntLibContrib.Resource.ResourceManager NOT System.Resources.ResourceManager
ResourceManager rm = ResourceFactory.GetResourceManager();
// get a string resource
string myString = rm["StringKey"];
// get an integer resource, this works for any type of resource
int myInt = (int)rm["IntegerKey", typeof(int)];
// get an audio resource, you would normally need to use the GetStream() method for this type of resource.
UnManagedMemoryStream myAudio = (UnManagedMemoryStream)rm["AudioKey", typeof(UnManagedMemoryStream)];

This next code sample shows how to get a named resource manager instance, set a specific culture and also how do do string formatting using the optional params parameter of the indexer:

[C#]

// get the "named instance" resource manager, this is the name you have given the configured resource manager in the console.
ResourceManager rm = ResourceFactory.GetResourceManager("named instance");
// set the culture to generic french.
rm.CultureInfo = new CultureInfo("fr");
// get a formatted string resource and format the string
string friendlyResponse = "bonjour";
string myFormattedString = rm["FriendlyMessageKey", friendlyResponse];

If the resource value is something like "mon ami dit {0}" then myFormattedString will contain "mon ami dit bonjour". Note: you can have more than one replaceable format string parameter in the same fashion as String.Format().

Installing the Assemblies

When you build the Resource Application Block the assemblies are compiled without a strong name key. If you want to put these assemblies into the GAC then you will need to assign a strong name key to each assembly and recompile (this is not neccessary for any design.dll assembly). If you use the BuildLibraryAndCopyAssemblies.bat console script then the assemblies are copied to the EntLibContrib bin folder. You can reference the assemblies from here for your application however; to use the Configuration console you will need to copy all of the following assemblies to your installation of the Enterprise Library Configuration Console which is usually in C:\Program Files\Microsoft Enterprise Library 3.1 - May 2007\Bin:

The Resource Application Block 3.1 consists of the following assemblies:

EntLibContrib.Resource.dll - the main assembly for the block
EntLibContrib.Resource.Store.dll - the Resource Application Block uses itself to supply its own resources. These are held in this resource only assembly.
EntLibContrib.Resource.Database.dll - to comply with the rule that all application blocks must be able to work independantly of any other block, the data resource manager and provider, which has a dependancy on the Data Access Application Block was separated out to its own assembly.
EntLibContrib.Resource.Configuration.Design.dll - the plug-in interface to the Enterprise Library Configuration Console for the Resource Application Block.
EntLibContrib.Resource.Database.Configuration.Design.dll - the plug-in interface to the Enterprise Library Configuration Console for the Resource Application Block data provider.

What Next?

Acknowledgements

I did not get much feedback from the Resource Application Block versions 1.1 and 2.0 so I very nearly did not bother with version 3.1 until I read .NET Internationalization by Guy Smith-Ferrier so my thanks to him for the inspiration and some neat ideas.

I know it might sound like a cliche but I must include my wife Margaret too. I have three young boys and you don't get to write this kind of stuff whilst carrying out a full program of fatherly responsibilities... Off to read Rupert Bear to the 6 year old, I will try not to localize him or turn Pong-Ping into a Frenchman.

UPDATED WIKI: Managers

ewdev — Sat, 08 Mar 2008 12:38:14 GMT

Resource Managers

The Resource Application Block Resource Manager type is actually a wrapper for any one of a set of Resource Managers that inherit from ExtendedComponentResourceManager which in turn inherits from the System.Resources.ResourceManager type. One example is the BinaryResourceManager.

The key method within the System.Resources.ResourceManager type is the InternalGetResourceSet() method which is responsible for obtaining a single set of resources for a single culture. It is also responsible for the fallback feature of resource management. For example, if you ask for resources for the culture fr-CA but this set of resources does not contain values for all the resources but you have all the common French resources in the generic set fr. Then resource managers will fetch resources from the fr-CA set first, if they exist, otherwise fallback to fetching resources from the fr set and so on until you reach the neutral or invariant culture.

The InternalGetResourceSet() method returns the set of resources as a ResourceSet type. Not only does the ResourceSet contain a single set of resources but it is also responsible for marshalling the correct IResourceReader and IResourceWriter for reading and writing the set of resources from a resource store.

The ExtendedComponentResourceManager

Microsoft wrote the ComponentResourceManager to work with their CodeDomLocalizationProvider and ResourceCodeDomSerializer to read and write localizable Windows Forms component properties to and from embedded assembly resources. The key feature of the ComponentResourceManager is the ApplyResources() method that takes a component and a key name and uses reflection to match resources to component properties. The Resource Application Block resource managers rely on several of the available constructors of the System.Resource.ResourceManager type, especially the one that takes a base name and an assembly. Although the ComponentResourceManager inherits from System.Resource.ResourceManager it only implements the constructor that takes a single Type. This made it unsuitable as a parent for the resource managers for the Resource Application Block. For this reason the ExtendedComponentResourceManager was written to implement all of the System.Resource.ResourceManager constructors and to provide the ApplyResources() method. Unfortunately, because it was not possible to inherit from the ComponentResourceManager this gives us big problems integrating with the Windows Forms designer for resource management, however not all is lost see Windows Forms Designer for more details.

In addition to the ApplyResources() method, the ExtendedComponentResourceManager also integrates with the Enterprise Library instrumentation interface to provide performance, monitoring and logging information.

Assembly Based Resources

This is the default resource storage type used by the System.Resource.ResourceManager so nothing special is needed beyond the ExtendedComponentResourceManager.

File Based Resources

Both Binary and Xml resource managers use file based resources. A FileResourceManager abstract type inherits from ExtendedComponentResourceManager and overrides the InternalGetResourceSet() method to handle the reading of resources from files. The BinaryResourceManager and XmlResourceManager both inherit from FileResourceManager to provide the appropriate ResourceSet type to the FileResourceManager's InternalGetResourceSet() method.

Database Based Resources

The DataResourceManager inherits from the ExtendedComponentResourceManager and overrides the InternalGetResourceSet() method to provide a DataResourceSet type to the method. The DataResourceSet handles reading resources from a database.

ResourceSets

All Resource Application Block ResourceSets inherit from the CommonResourceSet which in turn inherits from System.Resources.ResourceSet. One example is the BinaryResourceSet.

The key feature of a ResourceSet is to hold a table of resources for a single culture and, in addition, to associate a specific type of resource reader and resource writer with the resource set by providing the GetDefaultResourceReader() and GetDefaultResourceWriter() methods. Note: the GetString(), and GetObject() methods also come from ResourceSet called by similar methods within System.Resource.ResourceManager.

The CommonResourceSet adds a few additional features to the ResourceSet type such as a Count property to return the number of resources in its table, a Resources property to expose the inner table, a CreateDefaultResourceReader() and a CreateDefaultResourceWriter() to create an instance of an IResourceReader and IResourceWriter respectively. The methods included in the base type as described above only returned the type of default reader and writer. I have to give credit to Guy Smith-Ferrier for the inspiration on this one.

The Resource Application Block ResourceSets

There is no AssemblyResourceSet because this is the default type.

BinaryResourceSet - this serves to provide a BinaryResourceReader and BinaryResourceWriter to the InternalGetResourceSet() method.
XmlResourceSet - this serves to provide an XmlResourceReader and XmlResourceWriter to the InternalGetResourceSet() method.
DataResourceSet - this serves to provide a DataResourceReader and DataResourceWriter to the InternalGetResourceSet() method.

The resource readers and resource writers use the Enterprise Library to get their configuration. In addition to reading and writing to and from the configured resource store, these custom readers and writers also implement the IResourceDataNode interface for storing additional resource related data and custom types.

The IResourceDataNode Interface

The basic resource item in a set only carries a resource name key and a value. Using the IResourceDataNode interface the resource item can carry additional information that includes a comment, a type name and a file reference.

Comments* - These are simple strings associated with a resource item to give a human reader a description of the item for use with resource editors (*binary resources cannot support comments).
Type Names - This is essential for resource stores that do not store resources as serialized CLR types. This enables a resource editor to reconstitute the resource as its proper type for display and editing. For example, a colour resource can be reconstituted as a Color object and be displayed as a shape of the appropriate colour.
File References - A file reference is a pointer to an external file, typically a UNC name or Url. Xml resources use file references. An alternative to a file reference is to binary serialize the file contents into the resource store, this is the preferred option for binary and data resources.

UPDATED WIKI: The QuickStart Sample Applications

ewdev — Tue, 04 Mar 2008 00:20:15 GMT

The Resource Application Block QuickStart Sample Applications

The two samples that are supplied with the Resource Application Block are contrived to demonstrate all of the features of the Resource Application Block.

Note: before trying out the samples please check the configuration files with the Enterprise Library Configuration Console. The samples use file based providers with absolute path names. These files are quite likely to be in a different place on your computer as they were on mine.

The Windows Forms based Message of the Day Application

The key features demonstrated here are the standard mechanism for getting at resources, the strongly typed class method of getting at resources and the integration with the Windows Forms designer reflection-based component property resource management feature,

The application uses two resource managers, one for managing the messages of the day and another for managing the form resources:

[C#]

// Resource Manager holding the message resources. This is the default resource manager
// in configuration, hence no need to give the instance name.  This is also a Binary resource
// which means that the resources come directly from the "*.resources" files.
private ResourceManager messageResources = ResourceFactory.GetResourceManager();
// Resource Manager holding the form resources.  Because this is not the default resource manager
// you need to include the instance name. This is also an Xml resource which means that the 
// resources come directly from the "*.resx" file which can be edited independantly from the
// application.
private ResourceManager formResources = ResourceFactory.GetResourceManager("Form Resource Manager");

Also a strongly typed class was generated for the form resources and used in the MessageOfTheDay() method. This method also uses the standard mechanism for getting at resources.

[C#]

/// <summary>
/// Set the message of the day.
/// </summary>
/// <remarks>
/// The message of the day label is fetched from form resources using a strongly typed class,
/// while the message of the day text is fetched from message resources using an indexer.
/// </remarks>
public void MessageOfTheDay()
{
	// Message of the day label. Note the use of the generated strongly typed class
	// this class was generated from the Enterprise Library configuration tool
	string messageLabel = FormResources.labelMessageOfTheDay_Text;
	this.labelMessageOfTheDay.Text = messageLabel + ( (DayName)this.comboDays.SelectedItem ).NameValue;
 
	// Message of the day text. Here we use string manipulation to calculate the resource key
	// and then apply the key to the resource manager default indexer for string resources.
	string message = messageResources[( (DayName)this.comboDays.SelectedItem ).NameKey + "Message"];
	this.textMessage.Text = message;
}

Finally you see the reflection-based component property resource management feature in the ApplyResources() method

[C#]

/// <summary>
/// Reinitialize the form components that take localised information.
/// </summary>
/// <remarks>Note how we demonstrate the use of the ApplyResources method from the resource manager.
/// This method uses reflection to match resources found in the resource file with the properties of
/// a given form component.  For clarity I have used the exact same component key names as would
/// be generated by the Windows Form designer.  Have a look at the FormResources.resx file to see 
/// how these key names are formatted. Note how each property, except for the default property, takes
/// an initial double chevron.</remarks>
private void ApplyResources()
{
	this.SuspendLayout();
	formResources.ApplyResources(this, "$this");
	formResources.ApplyResources(this.comboCulture, "comboCulture");
	formResources.ApplyResources(this.comboDays, "comboDays");
	formResources.ApplyResources(this.labelMessageOfTheDay, "labelMessageOfTheDay");
	formResources.ApplyResources(this.pictureFlag, "pictureFlag");
	formResources.ApplyResources(this.textMessage, "textMessage");
	this.ResumeLayout(false);
}

The Web based Message of the Day Application

The key features demonstrated here are the implicit mechanism for getting at local resources using the web resource provider and the explicit mechanism for getting at both local and global resources using the web resource provider,

Here is an example of the implicit use of resources through the web resource provider, the resource manager base name will be the name of the web page class, which in this case is default:

[ASPX]

<asp:Image ID="logo" runat="server" ImageUrl="~/App.ico" meta:resourcekey="logoResource1" />
&nbsp;
<asp:Label ID="title" runat="server" Text="title" meta:resourcekey="titleResource1" CssClass="title"></asp:Label>

Here is an example of the explicit use of resources through the web resource provider to get the national flag Url, using the syntax for getting at global resources, and implicit use of local resource to get the other pictureImage control properties:

[ASPX]

<asp:Image ID="pictureImage" runat="server" ImageUrl="<%$ Resources:default, nationalFlagUrl %>" meta:resourcekey="pictureImageResource1" />

The code-behind class uses the standard method and the strongly typed method for getting at resources in the MessageOfTheDay() method:

[C#]

/// <summary>
/// Set the message of the day.
/// </summary>
/// <remarks>
/// The message of the day label is fetched from form resources using a strongly typed class,
/// while the message of the day text is fetched from message resources using an indexer.
/// </remarks>
public void MessageOfTheDay()
{
	// Message of the day label. Note the use of the generated strongly typed class
	// this class was generated from the Enterprise Library configuration tool
	//string messageLabel = PageResources.labelMessageOfTheDay_Text;
	this.messageLabel.Text = PageResources.messageLabelResource1_Text + this.comboDays.SelectedItem.Text;
 
	// Message of the day text. Here we use string manipulation to calculate the resource key
	// and then apply the key to the resource manager default indexer for string resources.
	this.message.Text = messageResources[this.comboDays.SelectedValue + "Message"];
}

UPDATED WIKI: The QuickStart Sample Applications

ewdev — Tue, 04 Mar 2008 00:15:59 GMT

The Resource Application Block QuickStart Sample Applications

The Windows Forms based Message of the Day Application

// Resource Manager holding the message resources. This is the default resource manager
// in configuration, hence no need to give the instance name.  This is also a Binary resource
// which means that the resources come directly from the "*.resources" files.
private ResourceManager messageResources = ResourceFactory.GetResourceManager();
// Resource Manager holding the form resources.  Because this is not the default resource manager
// you need to include the instance name. This is also an Xml resource which means that the 
// resources come directly from the "*.resx" file which can be edited independantly from the
// application.
private ResourceManager formResources = ResourceFactory.GetResourceManager("Form Resource Manager");

Also a strongly typed class was generated for the form resources and used in the MessageOfTheDay() method.

[C#]

/// <summary>
/// Set the message of the day.
/// </summary>
/// <remarks>
/// The message of the day label is fetched from form resources using a strongly typed class,
/// while the message of the day text is fetched from message resources using an indexer.
/// </remarks>
public void MessageOfTheDay()
{
	// Message of the day label. Note the use of the generated strongly typed class
	// this class was generated from the Enterprise Library configuration tool
	string messageLabel = FormResources.labelMessageOfTheDay_Text;
	this.labelMessageOfTheDay.Text = messageLabel + ( (DayName)this.comboDays.SelectedItem ).NameValue;
 
	// Message of the day text. Here we use string manipulation to calculate the resource key
	// and then apply the key to the resource manager default indexer for string resources.
	string message = messageResources[( (DayName)this.comboDays.SelectedItem ).NameKey + "Message"];
	this.textMessage.Text = message;
}

Finally you see the reflection-based component property resource management feature in the ApplyResources() method

[C#]

/// <summary>
/// Reinitialize the form components that take localised information.
/// </summary>
/// <remarks>Note how we demonstrate the use of the ApplyResources method from the resource manager.
/// This method uses reflection to match resources found in the resource file with the properties of
/// a given form component.  For clarity I have used the exact same component key names as would
/// be generated by the Windows Form designer.  Have a look at the FormResources.resx file to see 
/// how these key names are formatted. Note how each property, except for the default property, takes
/// an initial double chevron.</remarks>
private void ApplyResources()
{
	this.SuspendLayout();
	formResources.ApplyResources(this, "$this");
	formResources.ApplyResources(this.comboCulture, "comboCulture");
	formResources.ApplyResources(this.comboDays, "comboDays");
	formResources.ApplyResources(this.labelMessageOfTheDay, "labelMessageOfTheDay");
	formResources.ApplyResources(this.pictureFlag, "pictureFlag");
	formResources.ApplyResources(this.textMessage, "textMessage");
	this.ResumeLayout(false);
}

The Web based Message of the Day Application

The key features demonstrated here are the implicit mechanism for getting at local resources using the web resource provider and the explicit mechanism for geting at both local and global resources using the web resource provider,

Here is an example if the implicit use of resources through the web resource provider, the resource manager base name will be the name of the web page class in this case it is default:

[ASPX]

<asp:Image ID="logo" runat="server" ImageUrl="~/App.ico" meta:resourcekey="logoResource1" />
&nbsp;
<asp:Label ID="title" runat="server" Text="title" meta:resourcekey="titleResource1" CssClass="title"></asp:Label>

<asp:Image ID="pictureImage" runat="server" ImageUrl="<%$ Resources:default, nationalFlagUrl %>" meta:resourcekey="pictureImageResource1" />

The code-behind class use the standard method and the strongly typed method for getting at resources in the MessageOfTheDay() method:

[C#]

/// <summary>
/// Set the message of the day.
/// </summary>
/// <remarks>
/// The message of the day label is fetched from form resources using a strongly typed class,
/// while the message of the day text is fetched from message resources using an indexer.
/// </remarks>
public void MessageOfTheDay()
{
	// Message of the day label. Note the use of the generated strongly typed class
	// this class was generated from the Enterprise Library configuration tool
	//string messageLabel = PageResources.labelMessageOfTheDay_Text;
	this.messageLabel.Text = PageResources.messageLabelResource1_Text + this.comboDays.SelectedItem.Text;
 
	// Message of the day text. Here we use string manipulation to calculate the resource key
	// and then apply the key to the resource manager default indexer for string resources.
	this.message.Text = messageResources[this.comboDays.SelectedValue + "Message"];
}