I want to store additional information on my users (address, phone).
Should I extend the registration page on the sample mvc template or should I set up a separate “profile” table and have that be a separate page?
It seems nice to do it on the registration page, but I am not sure if there are issues playing around with the “aspnet_”… tables that are setup for registration.
Any suggestions? I would like to use LINQ to SQL as well if possible but I see the default implementation is using
System.Web.Security.membership
You could also consider creating custom Membership Provider.