Re: I feel it makes sense NOT to use custom membership & role provider

Tech-Archive recommends: Speed Up your PC by fixing your registry

:)

I decided to stick to provider, the only problem was 'providerUserKey'
- i still can't see elegant way to assign value to it

I wonder - why Microsoft put it as INPUT parameter into CreateUser
method with NO WAY to initialize it manually

So i see 2 ways:
1) easier, but not elegant at all - create session variable and use it
to keep extrafield info: initialize it in CreatingUser and read it
inside CreateUser - so providerUserKey parameter is just left
behind...
2) to make extra property for keeping these extra fields in extended
membershipprovider class. Since this class is a singletone, it should
keep a LIST of objects, where every list item corresponds to specific
userid (login id). So, we assign extrafield info to such object in
CreatingUser and read it inside CreateUser: the same idea as in method
1

.