Designing loosely coupled components in .NET - Provider Pattern

Question

I have been told that the Provider pattern is a way to design loosely coupled components. I am working on designing an API. Could you please point to links where Provider pattern is explained. I found one here, are there any more that describe provider pattern using .net as the framework

Answer 1

Here is a white paper from MSDN (linking to part 1)

Here is another source for Provider Design Patterns in ASP.NET 2.0 from C-Sharp Corner

Answer 2

MSDN offers a walk-through for the ASP.NET Provider Pattern

Answer 3

In Juval Lowy's WCF book he calls the pattern the Bridge pattern. dofactory has some good stuff on it too.

I've recently been collecting some links on the provider pattern for an MS exam I was studying for (70-568). Here's the list- more than you'll ever need to know about the Provider Model:

• Provider Model Design Pattern and Specification, Part 1 (old but detailed).
• The ASP.NET 2.0 Provider Model. 136 pages- a tomb of Provider Model information.
• ProviderBase- the base class for all provider implementations.
• Don’t forget to add <clear/> when adding providers.
• Configuring Providers.
• Using the ASP.NET provider functionality in Windows based apps.
• Implementing a Membership Provider.
• Implementing a Role Provider.
• Creating a custom site map provider.
• Implementing a Profile Provider.
• Creating a custom DB profile provider.
• Session State Providers.
• Implementing a Session-State Store Provider.

Answer 4

Hi, the most elegant solution for achieving loose coupling is DI and IoC.

Have a look here:

• Design Pattern IoC and DI
• Inversion of Control and Dependency Injection: Working with Windsor Container

Have fun :)