Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1218
  • Last Modified:

Entries into dbo.Users, not dbo.aspnet_Users

I have migrated some ASP.Net 2.0 code to ASP.Net 4.5 and am having a problem with adding users and roles. The new information is going into a table dbo.Users in the aspnetdb database rather than dbo.aspnet_Users as it used to. Why is this and how do I get it to work as before? Is there a new API I should be using?
0
steve_webber
Asked:
steve_webber
  • 5
  • 3
1 Solution
 
Manoj PatilSr. Software EngineerCommented:
Just replace this,

 <membership defaultProvider="DefaultMembershipProvider">
      <providers>
        <add name="DefaultMembershipProvider" type="System.Web.Providers.DefaultMembershipProvider, System.Web.Providers, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" connectionStringName="DefaultConnection" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="false" requiresUniqueEmail="false" maxInvalidPasswordAttempts="5" minRequiredPasswordLength="6" minRequiredNonalphanumericCharacters="0" passwordAttemptWindow="10" applicationName="/" />
      </providers>
    </membership>

Open in new window


with this,


<membership defaultProvider="DefaultMembershipProvider">
      <providers>
        <add name="DefaultMembershipProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="DefaultConnection" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="false" requiresUniqueEmail="false" maxInvalidPasswordAttempts="5" minRequiredPasswordLength="6" minRequiredNonalphanumericCharacters="0" passwordAttemptWindow="10" applicationName="/" />
      </providers>
    </membership>

Open in new window

0
 
steve_webberAuthor Commented:
This did not work. I created my aspnetdb database using aspnet_regsql.exe and all of the tables within the database so created have their names prefixed with "aspnet_". The views created reference the tables with these names. However, when I try to execute

      Roles.CreateRole("Administration")
      Membership.CreateUser("admin@appforms.com", "foobar123", "admin@appforms.com")
      Roles.AddUserToRole("admin@appforms.com", "Administration")

it creates new tables which do not have "aspnet_" at the beginning of the names. It places the new role in the dbo.Roles table and can't add the user because it is looking for dbo.aspnet_Roles (via the views which still reference dbo.aspnet_Roles).
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
steve_webberAuthor Commented:
It appears that the new user was added to the ado.aspnet_Users table, but the role was added to ado.Roles table and the error occurs trying to add the user to the role.
0
 
Manoj PatilSr. Software EngineerCommented:
Can you specify the error.
0
 
steve_webberAuthor Commented:
The error returned was "The user 'admin@appforms.com' was not found." I assume this is because it was looking in dbo.Users instead of dbo.aspnet_Users.
0
 
steve_webberAuthor Commented:
The problem was that I should not have tried to use aspnet_regsql.exe at all. This is apparently all automatic with ASP.Net 4.5. I am using the web.config that was generated by default and it works fine. I'm not sure why it was referencing the aspnet_Roles table, and I'll try to figure this out.
0
 
steve_webberAuthor Commented:
I determined by myself that i was using an obsolete mechanism to create the membership database. It is created automatically, with different table names, with ASP.Net 4.5.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now