Question

1) Is there a reason why aspnet_Profile table doesn’t have ApplicationId column, while aspnet_Membership and aspnet_Roles tables do define ApplicationID columns?

2) If we create a profile for current user and then change the applicationName of our profile provider, then profile for same user couldn’t be read anymore. So it seems profile provider somehow knows that table entry for this user was made before applicationName was changed?

But how is that possible, since aspnet_Profile doesn’t contain ApplicationID column?

Thank you

EDIT:

2) I don t see how to change the application name of a profile provider - it is not an attribute of a provider entry in the profile section. It IS an attribute of a provider in the membership section, which makes sense

I was able to specify applicationName attribute, so I must assume profile provider does use it in some way:

   <profile defaultProvider="defaultP">
    <providers>
      <add name="defaultP"
           connectionStringName="connect"
           applicationName="_someName"

Answer 1

1) Looking at the database tables for the aspnet security system, a Profile record is tied to a user, and a user is tied to an application. Since all profiles are tied to users, the profile itself doesn t need to explicitly specify an application (this is implied by the user s application).

2) I don t see how to change the application name of a profile provider - it is not an attribute of a provider entry in the profile section. It IS an attribute of a provider in the membership section, which makes sense.

友情链接