SqlServerMembershipProvider bug or "feature"

S

scottrudy

I was trying to set up adhoc providers so that users can be managed for
sub-sites by the sub-site owners. I figured I would just copy the existing
user over from the default provider so that I could maintain the same UserId
across applications. However, I am a little confused about lines 103 and 126
(if you select modify from the SSMS context menu) in the stored procedure
aspnet_Membership_CreateUser. The key to the Membership and Users tables is
ApplicationId and UserId, yet an exception is thrown if two different
ApplicationIds use the same UserId. Following the same pattern, then the
LastUpdatedDate is updated for the user for all applications.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,755
Messages
2,569,536
Members
45,012
Latest member
RoxanneDzm

Latest Threads

Top