Each user who had these additional properties set would have exactly one record in the column.Imagine we were building a web application that uses Membership, but needed to track three additional, optional data points for each user: a bio, the user's birth date, and the URL to the user's website.Next, add App_Code folder to the web site and add a new class in it. They represent the respective columns of the Photos table.
NET Framework that supports creating, authenticating, deleting, and modifying user account information.
Each user account has a set of core properties: username, password, email, a security question and answer, whether or not the account has been approved, whether or not the user is locked out of the system, and so on.
These user-specific properties are certainly helpful, but they're hardly exhaustive - it's not uncommon for an application to need to track additional user-specific properties.
The second option is to use the Profile system, which allows additional user-specific properties to be defined in a configuration file.
(See Part 6 for an in-depth look at the Profile system.) This article explores how to store additional user information in a separate database table.