ASP.NET Provider Pattern

I’ve been vaguely aware of discussions flying around the ASP.NET community about the provider pattern which is being introduced with Whidbey (BETA 1 out now, check it out).

One of the most active participants in the discussion has been Paul Murphy which has pointed out what he feels are a few deficiencies in the model. Paul has decided to posted his final thoughts on the subject and he suggests some good ideas and offers up some code to ponder. Both the post and the code are both definately worth the read.

I would point out that unless you are providing a “feature”, a few switches in the configuration file is about all you are going to need to know about the provider architecture unless you need to do some integration work with existing systems. And I think that is an important point to remember. Whatever pattern is optimal (if there is such a thing) its really much more important to factor the feature interface so that it is usable.


One thought on “ASP.NET Provider Pattern

  1. cJ

    hey i need some help in exception handling and logging application block…
    i want to use my daily activity event detection rather than error/exception ,And want a report of that event/activity via email….i searched the whole Enterprise library but i could not find the exact coding of that exception pickup point by logging handler…
    that will be very helpful to me if u could help me.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s