Provider Aggregator Pattern is an extension of Provider Pattern, which enables us to create and utilize multiple instance of the class having the same provider interface. In this pattern, there is an Aggregator class which implements the provider interface and contains a collection of instances of c...

We just finished the final iteration for this and went gold. Although this post has more marketing then I would normally post here, I at least wanted to let fellow Linq fanatics that our 'semi-secret' project with a few companies you might know has at least for now reached a milestone. And who co...

In this article Keyvan teaches you how to write your own data provider for .NET applications using the provider model.

Recently, I did couple of posts regarding how to create a custom LINQ provider, I even created a project at Codeplex named LINQ.Flickr, that makes querying , adding and deleting photos , overall creating Flickr app much more enjoyable , with query flavor, similar to LINQ to SQL .....

A SiteMapProvider implementation for large web applications with static pages. An alternative to the default SiteMapProvider using a web.stemap file.

Find out how to create a data drive ASP.NET resource provider that uses database data for localization and use ASP.NET to edit resources in real time as part of your application. This post is a compilation of links to the primary article, online samples, another Introduction to Localization artic...

Haacked discusses why using the Database as an Integration point is generally a bad practice, and even gives a real world example from the OSS community.

I still think the Provider model -- which handles high-level concepts like site membership, roles, and personalization, but allows you to modify the way they work at a low level by swapping in and out new providers -- is one of the coolest [...] things.

I will describe how to create a Rules Engine Framework using C#. It will take a few posts to describe the entire process but it's very cool and your going to want to read them all. In Part 1, I am going to describe the Rules Provider.

For the past 15 or so years, if you wanted to create a pluggable architecture, you used Interfaces. They define a signature that classes must implement in order to conform to that Interface. He says that this is the best way to go, and he is incorrect. I can see where he is coming from though, so le...

I remember when the provider model first came out and how I latched onto it like a duck on a june bug :) Many of the applications delivered to customers soon after its introduction used the provider model, especially for the data access layer.

This article focuses on the Provider Model design pattern and describes how it can be used to solve certain problems. To help readers to better understand or appreciate this design pattern, I've chosen view state management as an example to demonstrate the usefulness and practicality of this design ...

Class library that fully implements the RSS 2.0 specification, and provides a provider based syndication model for uniform interface between feed data sources and RSS services. Includes a SQL server syndication provider and database installation scripts.