title: Using a model for multiple purposes
body: <p>I'm new to ASP.NET MVC using Entity Framework and I'm trying to create a simple login system. At the moment I have <code>UserProfile</code> model that I wish to model a login form off of.</p>
  
  <p><strong>UserProfile.cs</strong></p>
  
  <pre><code>namespace MyProject.Areas.Admin.Models
  {
      public class UserProfile {
  
          [Key]
          public int UserID { get; set; }
  
          [Required]
          [Display(Name = "Username")]
          public string Username { get; set; }
  
          [Required]
          [DataType(DataType.Password)]
          [Display(Name = "Password")]
          public string Password { get; set; }
  
          public string FirstName { get; set; }
          public string Surname { get; set; }
          public string EmailAddress { get; set; }
          public string Telephone { get; set; }
  
      }
  }
  </code></pre>
  
  <p>As my login form will only require a username and password, is it correct for me to create a separate model (for instance, a <code>LoginModel</code> with just those properties, or should I contine to use the <code>UserProfile</code> model?</p>
  
  <p>It feels better for me to create a separate model to model the login submission, but then I run into the issues such as making them reference the same table?</p>
  
  <p>Thanks</p>