How to enable Migrations to Identity in Asp.net MVC

Question

I need to decouple Identity from my Asp.net core MVC layer and play it for another crosscutting layer of my DDD project. Based on Eduardo Pires' Equinox project, I was able to do it, but I’m finding it difficult to activate Migrations. So you’ll understand what I’ve done:

1 - I created the Commercial.Presentation.Web.MVC layer with user authentication. Automatically, the system created several folders, controllers, and classes needed for authentication to work, including the local database. Fantastic!!!!

2 - I created a Commercial System layer.Infra.Crosscutting.Identity.Data and manually created the same folders, controllers and classes as the mvc layer. The idea is to activate Migrations on this layer and then I remove everything from the MVC layer and in this way, the operation would be decoupled and in the Identity layer.

When I try to run "Add-Migration Initialcreate -Context: Applicationdbcontext", the following error msg appears:

Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[0] User profile is available. Using 'C:* Local ASP.NET Dataprotection-Keys' as key Repository and Windows DPAPI to Encrypt Keys at Rest. More than one Dbcontext named 'Applicationdbcontext' was found. Specify which one to use by providing its Fully Qualified name using its Exact case.

 //Minha classe de contexto na camada Identity
 
 public class ApplicationDbContext : IdentityDbContext<ApplicationUser>
    {
        public ApplicationDbContext(DbContextOptions<ApplicationDbContext> options)
            : base(options)
        {

        }

        protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
        {
            // get the configuration from the app settings
            var config = new ConfigurationBuilder()
                .SetBasePath(Directory.GetCurrentDirectory())
                .AddJsonFile("appsettings.json")
                .Build();

            // define the database to use
            optionsBuilder.UseNpgsql(config.GetConnectionString("DefaultConnectionpg"));
        }
        
    }

Does anyone know how to help me activate Migrations in the created Identity layer?

Project link: https://onedrive.live.com/? id=40838E65B9F8787E%21120&Cid=40838E65B9F8787E

Answer 1

He’s complaining because you have two context with the same name (Applicationdbcontext.Cs) within your solution.

The solution is to delete your Context from your MVC layer or rename any of the contexts, since you specify the context name in the powershell line:

-Context: ApplicationDbContext