Home/ Questions/How to fix the entity type applicationuser is not part of the model for the current context.?
Answered
Annabel Jacobi
  • 0
Asked: 2022-08-16T10:22:30+00:00 In:

How to fix the entity type applicationuser is not part of the model for the current context.?

  • 0

. Advertisement .

..3..

. Advertisement .

..4..

 

I got the error message below: the entity type applicationuser is not part of the model for the current context.

I’m very confused because this error took me a lot of time to find a solution but it hasn’t worked. What does the above error mean? How can I handle it quickly.

Please help me. Thanks in advance.

Share

1 Answer

  1. Best Answer
    Expert

    The cause:

    You’ll probably run into this issue if you’re utilizing the connection string created while importing the EDMX file using in:base(“EDMXConnString”).

    Solution: By establishing a common connection string that referred to the database containing the ASP.NET Identity tables, you were able to resolve the error: the entity type applicationuser is not part of the model for the current context.

    <add name=MyConnString connectionString=Data Source=server; Initial Catalog=db_name; User ID=user_id; Password=password; Connect Timeout=60; providerName=System.Data.SqlClient />

    It then will work when you use the connection string in :base.

    public class ApplicationDbContext : IdentityDbContext<ApplicationUser>
{
public ApplicationDbContext()
: base(MyConnString)
{
}
}

    To ensure that a context instanciation is not missed, the code should be as follows:

    UserManagerFactory = () => new UserManager<ApplicationUser>(new UserStore<ApplicationUser>(new ApplicationDbContext()));
    • 0

Leave an answer

You must login to add an answer.

Need An Account,