RE: Pointed in the right direction?
- From: wawang@xxxxxxxxxxxxxxxxxxxx (Walter Wang [MSFT])
- Date: Tue, 15 Aug 2006 06:53:22 GMT
Hi Eric,
Based on my understanding, your question is how to use the Provider design
pattern in your application. Please feel free to post here if I've
misunderstood anything.
The theory of this pattern is that it allows to define a well-documented,
easy-to-understand API, but at the same time give developers complete
control over the internals of what occurs when those APIs are called.
Defined, a provider is simply a contract between an API and the Business
Logic/Data Abstraction Layer. The provider is the implementation of the API
separate from the API itself. For example, the Membership feature has a
static method called Membership.ValidateUser(). The Membership class itself
contains no business logic; instead it simply forwards this call to the
configured provider. It is the responsibility of the provider class to
contain the implementation for that method, calling whatever Business Logic
Layer or Data Access Layer is necessary.
To learn how to use this design pattern, you may read the source code of
built-in ASP.NET 2.0 Membership, Role Management, Site Navigation, Session
State, Profile, Web Events, and Web Part Personalization providers:
http://weblogs.asp.net/scottgu/archive/2006/04/13/Source-Code-for-the-Built_
2D00_in-ASP.NET-2.0-Providers-Now-Available-for-Download.aspx
Or you can learn from how to implement the Provider design pattern in
ASP.NET 1.1:
http://msdn.microsoft.com/asp.net/downloads/providers/default.aspx?pull=/lib
rary/en-us/dnaspnet/html/asp04212004.asp
Hope this helps. Please feel free to post here if anything is unclear.
Sincerely,
Walter Wang (wawang@xxxxxxxxxxxxxxxxxxxx, remove 'online.')
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Follow-Ups:
- Re: Pointed in the right direction?
- From: Eric Cathell
- Re: Pointed in the right direction?
- References:
- Pointed in the right direction?
- From: Eric Cathell
- Pointed in the right direction?
- Prev by Date: RE: Threading Callback
- Next by Date: Re: Exception Management
- Previous by thread: Pointed in the right direction?
- Next by thread: Re: Pointed in the right direction?
- Index(es):
Relevant Pages
|