littleguru wrote:I'm not a big fan of the login components that come with ASP.NET 2.0 and the whole user management that comes with it.
It does not fit my goals. They create some kind of access database where you store the information. I could not figure out how to use objects to store the information, or a custom framework to get the information or store it...
I usually program them by myself, since it is not a big work.
They use the 'provider' model to access the database, so you 'only' need to write a provider to make the UI work with your database.
(Page takes a few seconds to load, looks like there is nothing there for some time..)
I have the same dilema at the moment, I have a suite of membership controls and I can't decide if I should dump my UI and write a membership provider or spruce up the UI componets with that nice expand to template functionality. I should add this is my 'learning' site so I might end up doing both
The thing that bugs me about the MS controls is the data access and logic are in the same class, so if you want to simply move to MySql but keep the schema you have to re-write both parts.