Re: Personalization question

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.

"Cirene" <cirene@xxxxxxxxxxx> wrote in message news:uDqeEW7EJHA.3616@xxxxxxxxxxxxxxxxxxxxxxx
It almost seems more beneficial for me to create my own table to store this info. Or am I missing something?

Thanks!

"Hillbilly" <somebody@xxxxxxxxxxxxx> wrote in message news:%235FEIB6EJHA.3996@xxxxxxxxxxxxxxxxxxxxxxx
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" <cirene@xxxxxxxxxxx> wrote in message news:%23cDlxD3EJHA.4904@xxxxxxxxxxxxxxxxxxxxxxx
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?





.

Relevant Pages

  • Re: the membership of asp.net2.0 is useful in my case?
    ... Its not a matter of like or dislike. ... > membership or profile). ... > Profile provider that works with all the UI controls just the same as the ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: MAPI property value
    ... (global profile section or my Address Book ... Provider's private profile section?) ... // Custom properties used by this service provider. ... The call in IABProvider::Logon opens first the some x section, ...
    (microsoft.public.win32.programmer.messaging)
  • Re: ASP.HttpProfile to be undefined
    ... Since there is a provider in there,"AspNetSqlProfileProvider", I don't need ... Look for the "profile" section: ... There is Intellisense for ASP but the 3 items do not include HttpProfile ... I'm using SQL Server and the AspnetDb database. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Architecture: Custom Profile Provider with Active Directory Membership
    ... While you can perform insert/update/delete operations on users, the one thing that you can't change is the username. ... So, it stands to reason that if you perform a rename in AD, you are doing it outside of the context of the MembershipProvider, and unfortunately, it would be up to you to relocate profile information for any accounts that you changed the name of. ...
    (microsoft.public.dotnet.languages.csharp)
  • Custom Profile Provider
    ... Ok, when I first started to play with the Provider model for all things membership in ASP.NET 2.0, I have to say I was pleased... ... I'd like to have profile be a strongly typed complex object derived from profilebase. ... Should I just scrap the profiles all together and somehow assign equivalent of a profile on Authentication? ... It looks like it was designed to be able to use custom strongly typed complex objects, I just don't know how to populate the object. ...
    (microsoft.public.dotnet.framework.aspnet.security)