I love the new provider pattern and Login Controls for ASP.NET 2.0, but whats up with the profile provider?? Its a great idea and all, but jamming a whole bunch of different data types into one field, that's bad database design! They should have their
own columns.
It also makes it harder to query and index...
So I guess my only option is to code my own MembershipProvider - not the end of the world, but it kinda defeats the purpose of the ProfileProvider
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.