Hello,

What advantage do you get with a custom provider over the default Provider (for example, using a default MembershipProvider instead of a custom one), or do you have to use a custom provider?

Thanks,

Brian

__________________
Brian

You may have an employee's organizational data in an LDAP directory and their benefits package identifier in DB2 database. You could create two providers, one that exposes the LDAP directory, and another that exposes the DB2 database. In many cases, you will already have components that provide access to this data, and the provider will be little more than a wrapper that allows the existing component to participate in the personalization framework. To support such scenarios, the personalization framework allows you to create your own providers...

http://msdn.microsoft.com/library/de...ionwhidbey.asp