EF Code-first MVC: Should I add fields to the default AspNetUsers table or create another 'UserInfo' table that relates to the AspNetUsers table?

Question

I am making a simple MVC application using code first entity framework. I'm trying to use the built in user registration/login. It provides me the default AccountController and ASP User tables.

My other entities are Players, Games, and Tournaments:

public class Player
{
    public int Id { get; set; }
    public string FirstName { get; set; }
    public string LastName { get; set; }
    public List<Game> Games { get; set; }
    public List<Tournament> Tournaments { get; set; }
}

public class Game
{
    public int Id { get; set; }
    public string Title { get; set; }
    public List<Player> Players { get; set; }
    public List<Tournament> Tournaments { get; set; } 
}

 public class Tournament
{
    public int Id { get; set; }
    public List<Player> Players { get; set; }
    public List<Game> Games { get; set; }

}

EF provides these tables.

Everyone who logs in is a player. I want each player to have a password and username. Should I remove my Players table and add the Player properties to the provided User class and AspNetUsers table? Or should I use a foreign-key to create a relationship between the Players table and the AspNetUsers table?

Are either or both of those options possible/preferable?

Also just a note, there will be additional properties in the Players, Games, and Tournaments classes; I was just starting with the basics.

Thank you very much for your time. Let me know if I am being unclear or if you need any additional information.

EDIT: Just found this: http://blogs.msdn.com/b/webdev/archive/2013/10/16/customizing-profile-information-in-asp-net-identity-in-vs-2013-templates.aspx

It shows something like both methods I described above. What is the advantage of adding a new UserInfo table vs. adding fields to the existing table?

If the info in the `Player` class is required to sign up, then it should be part of the `User` table — ediblecode, Jun 24 '15 at 14:31

score 0 · Answer 1 · answered Nov 23 '15 at 21:14

I would add this property to the player table:

public virtual ApplicationUser User { get; set; }

where ApplicationUser is the table that was given out of the box by Visual Studio. The ApplicationUser uses identity so when user creates a new player, have the playerController's Create action to set the user id of the user to the player id in the player table:

var userId = User.Identity.GetUserId();
Player.PlayerId = userId;

score -1 · Answer 2 · answered Jun 24 '15 at 15:45

-1

Add properties to ApplicationUser class. Also I suggest you to rename it to Player, so code will better match domain language.

answered Jun 24 '15 at 15:45

ranquild

1,799
1
16
25

Thank you very much for reaching out. I tried to add properties to ApplicationUser `FirstName` and `LastName` are not ending up in my database after migrations and I am getting a `500 Internal Server Error` when trying to register a user with a first name and last name. [I made a post about it here](http://stackoverflow.com/questions/31034931/http-post-resulting-in-500-internal-server-error-with-c-sharp-mvc-after-addin). Please let me know if you have any ideas as to what might be causing this. Thank you for your time – user95227 Jun 24 '15 at 19:16
@ranquild answer is totally useless to the OP. – Jhourlad Estrella Oct 20 '15 at 16:43

EF Code-first MVC: Should I add fields to the default AspNetUsers table or create another 'UserInfo' table that relates to the AspNetUsers table?

2 Answers2

Linked