The provider object model, as present in ASP.NET 2.0, is a great stepforward from hand-coded behavior in ASP.NET 1.x. But the provider modelis only as useful as are available providers.
Microsoft .NET itself contains set of profiles which can store their data in Microsoft SQL Server database: SqlMembershipProvider, SqlRoleProvider and SqlProfileProvider.However, database structure used by these providers is prettycomplicated and almost impossible to interconnect with your own tablesetc. Drop the “almost” for profile provider.
So I created set of my own providers and called them SimpleSqlMembershipProvider, SimpleSqlRoleProvider and SimpleSqlProfileProvider.They are simple in two ways: first, they are sort of minimalimplementation and do not have the full functionality of built-inproviders. Second, they use simple table structure (one table perprovider, role provider has two), which can be linked to other databasestructure as usual.
These providers are of course written in100% managed code (C#) and are totally independent on each other. Soyou may for example use my profile provider if you like it and keepusing whatever else provider for membership. This should be generaltruth, but in reality it isn’t. For example, the Table profile provider samples,although having the same virtue of simple table structure for profileproperties, are internally dependent on default SQL Membership Providerand cannot be used with any other.
