Home/ Questions/Q 626157
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T19:23:16+00:00

I’m just starting a new project on ASP.NET MVC and this will be the

  • 0

I’m just starting a new project on ASP.NET MVC and this will be the first project actually using this technology. As I created my new project with Visual Studio 2010, it created to my sql server a bunch of tables with “aspnet_” prefix. Part of them deal with the built-in user accounts and permission support.

Now, I want to keep some specific information about my users. My question is “Is it a good practice changing the structure of this aspnet_ tables, to meet my needs about user account’s information?”.

And as i suppose the answer is “No.” (Why exactly?), I intend to create my own “Users” table. What is a good approach to connect the records from aspnet_Users table and my own custom Users table.

I want the relationship to be 1:1 and the design in the database to be as transparent as possible in my c# code (I’m using linq to sql if it is important). Also, I don’t want to replicate the usernames and passwords from the aspnet_ tables to my table and maintain the data.

I’m considering using a view to join them. Is this a good idea?

Thanks in advance!

EDIT: From the answer, I see that I may not be clear enough, what I want. The question is not IF to use the default asp.net provider, but how to adopt it, to my needs.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If you are choosing to use the Membership API for your site, then this link has information regarding how to add extra information to a user.

    I was faced with the same scenario recently and ended up ditching the membership functionality and rolled my own db solution in tandem with the DotNetOpenAuth library.

    • 0