You can use the Profile provider, but there is a flaw in ASP.NET by default, where it basically stores all the values ββin a single field. This makes it difficult when you have something outside of ASP.NET that should use these values ββ(for example, for reporting purposes).
If this is not a problem, use Profile as Tim has linked, otherwise I would have created a separate table with the user's GUID as a key and simply bound it this way.
source share