Personalization question

[Cirene]

I have been looking into Personalization, Membership and Role Management.

If I understand it correctly, I should use Personalization to store extra
info about the user, such as:
First Name, Last Name, City, State, Zip, Birth Date, Last Login, Etc....

Is it a problem if later (like in a few months) I have to add additional
Profile items, such as Phone Number, etc... or delete existing profile
items? Will everything be managed automatically?

Do I basically get the point?

 

[Hillbilly]

1stly, Learn about the Profile Table Provider and why Scott Gu had to
release the Table Provider --after-- 2.0 itself was released when developers
discovered the default Profile provider stored data in a delineated object
making it quite impossible to query data in so many words. So read Scott
Gu's blog on this matter and get the Table Provider.

2ndly, yes, we can add new fields and their types to the table anytime.
Neither of the Profile Providers support foreign keys and related tables.
The System.Web.Security.Membership class is used to NURD all Profile data
via the provider you configure in your web.config file.

 

[Cirene]

It almost seems more beneficial for me to create my own table to store this
info. Or am I missing something?

Thanks!

 

[Hillbilly]

Using Membership is fast and efficient because its all built in but not
scalable it seems so yes, if you want or need relational Profiles use
ADO.NET. An example that could require justifying the use of ADO.NET would
be a person with Profile data using your application as an individual and
that same person having Profile data while using your application as a
member of some company.

It comes down to how liberal or strict you manage normalization.