I'm using the .Net Membership for dealing user validations. The client wants to store more data on users, i.e. the obvious stuff such as address, contact details. They also want to store marketing information, stats on how often each user has done certain things.
I'm against using the Profiles to do this since each of the properties is essentially a string with offsets and lengths to access them. Plus I'm sure I remember reading in a book that all profile data for a user is retrieved even if just one property is requested?
So my plan is top use the .Net membership just for user validation/assigning to roles and create our own tables in the ASP membership schema, sound ok? I don't like creating custom tables in existing, well defined schemas but I think avoiding the Profiles is the way to go , especially with future expansion in mind.
Thanks ...
Go to the complete details ...