There is an unsaved comment in progress. You will lose your changes if you continue. Are you sure you want to reopen the work item?
Migrations: Add-Migration ConfigurationTypeName and Name oddity
There is two contexts in the same DLL and I need to create initial migration for both contexts. I'm giving ConfigurationTypeName and Name parameters to Add-Migration cmdlet and it succeeds for the first context. When I'm running the same Add-Migration
command with same Name (="Initial" in my case) but different ConfigurationTypeName, it re-scaffolds the migration in the wrong context. It seems that the Name parameter preceeds the ConfigurationTypeName even though it shouldn't.