About custom MembershipProvider

[ChrisTorng]

I am studing VS 2005 Feb CTP, and thinking how to use those new features to
my new web project. I think the currently implemented MembershipProviders is
useless, because if I want to add a new field like phone/address, I must
write my MembershipProvider, and all related MembershipUser,
MembershipUserCollection... right? The real web sites always has more user
fields important.

[Paul Glavich [MVP ASP.NET]]

This question is really more suited to a Whidbey/V2 related list, however
you can use the Profile features to define custom profile properties in the
web.config. You can define them with (going from memory here so syntax may
be a little wrong or outdated)

<profile>
<properties>
<add name="Address1" type="System.String" />
<add name="Phone" type="System.String" />
</properties>
</profile>

These properties then become strongly typed properties that can be accessed
via intellisense through the 'Profile' property from your web page.

Also, here is a link to personalisation in 2.0
http://msdn.microsoft.com/asp.net/wh...nalization.asp

--

- Paul Glavich
ASP.NET MVP
ASPInsider (www.aspinsiders.com)
"ChrisTorng" <Ch********@discussions.microsoft.com> wrote in message
news:94**********************************@microsof t.com...

I am studing VS 2005 Feb CTP, and thinking how to use those new features to my new web project. I think the currently implemented MembershipProviders is useless, because if I want to add a new field like phone/address, I must
write my MembershipProvider, and all related MembershipUser,
MembershipUserCollection... right? The real web sites always has more user
fields important.