Forceful reset of Entity Framework Migrations

Question

I had an issue where some of my migrations weren't quite working and I didn't seem to be able to fix it. Therefore I decided to start again. I did the following:

Deleted the migration history table in the database
Deleted all the EF tables
Deleted the migrations folder from my project
Uninstalled EF5 via NuGet.

I then re-installed EF5 and ran the following;

Enable-Migrations –EnableAutomaticMigrations -Force

This creates my migration.cs file but doesn't touch the database. If I run some code that tries to use the context it complains that the tables don't exist. So I then created a migration:

Add-Migration InitialCreate

The migration this creates however has remembered some state, ignoring the fact it needs to create tables and just lists:

 public partial class InitialCreate : DbMigration { public override void Up() { AddColumn("dbo.NetC_EF_ShippingRate", "CurrencyName", c => c.String()); AddColumn("dbo.NetC_EF_ShippingRate", "CreationDate", c => c.DateTime(nullable: false)); } public override void Down() { DropColumn("dbo.NetC_EF_ShippingRate", "CreationDate"); DropColumn("dbo.NetC_EF_ShippingRate", "CurrencyName"); } }

How can I get it to forget the state fully and create all tables etc related to the context as if I was starting from scratch?

EDIT I should probably add if I simply try and run this manually created migration I just get errors:

Cannot find the object "dbo.NetC_EF_ShippingRate" because it does not exist or you do not have permissions.

App.config

<?xml version="1.0" encoding="utf-8"?> <configuration> <configSections> <section name="entityFramework" type="System.Data.Entity.Internal.ConfigFile.EntityFrameworkSection, EntityFramework, Version=4.4.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" /> <!-- For more information on Entity Framework configuration, visit http://go.microsoft.com/fwlink/?LinkID=237468 --></configSections> <entityFramework> <defaultConnectionFactory type="System.Data.Entity.Infrastructure.LocalDbConnectionFactory, EntityFramework"> <parameters> <parameter value="v11.0" /> </parameters> </defaultConnectionFactory> <!--<providers> <provider invariantName="System.Data.SqlClient" type="System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer" /> </providers>--> </entityFramework> <connectionStrings> <add name="FreightContext" providerName="System.Data.SqlClient" connectionString="Persist Security Info=False;database=DS_Kentico;server=FS-01\DEVSQL2008R2;user id=****;password=****;Current Language=English;Connection Timeout=240;" /> </connectionStrings> <startup> <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" /> </startup> </configuration>

web.config

<connectionStrings> <clear /> <add name="CMSConnectionString" connectionString="Persist Security Info=False;database=DeltaShelving_Kentico;server=FS-01\DEVSQL2008R2;user id=generic_webuser;password=generic_webuser;Current Language=English;Connection Timeout=240;" /> <add name="FreightContext" providerName="System.Data.SqlClient" connectionString="Persist Security Info=False;database=DS_Kentico;server=FS-01\DEVSQL2008R2;user id=****;password=****;Current Language=English;Connection Timeout=240;" /> </connectionStrings>

As I understand it, neither of the two commands you used Enable-Migrations or Add-Migration actually push anything to the database. The command to do that is Update-Database. However, the fact your migrations don't include any create table calls is a bit strange. Do the tables still exist in the database? — Richard
– Richard, Commented Apr 23, 2014 at 14:50
@Richard: I believe you're correct with your statement. No, I removed the tables from the database which is why I'm so confused. — Ian
– Ian, Commented Apr 23, 2014 at 14:52
@Richard: I think I've tracked down part of the problem. The verbose flag on a bad migration shows that it's pointing to the wrong database: Target database is: 'NetC.CustomModules.Freight.FreightContext' (DataSource: (localdb)\v11.0, Provider: System.Data.SqlClient, Origin: Convention). Unfortunately I can't find the string in any config files. Both my app.config and main web.config appear correct — Ian
– Ian, Commented Apr 23, 2014 at 14:56
ah ok. The database name its trying to find is derived based on convention. In the absence of any explicit connection string, EF will use the name of your custom DbContext as the db name. It also trying to look for a connections string with the same name first. So in your case it will be looking for a connection string called "FreightContext" and failing to find it — Richard
– Richard, Commented Apr 23, 2014 at 14:59
@Richard: I think that got it. Wrong startup project = missing app.config so it's tried to update the wrong database. Setting the correct project seems to fix it. Can you add your suggestion as an answer? — Ian
– Ian, Commented Apr 23, 2014 at 15:12

Richard · Accepted Answer · 2014-04-23 15:19:53Z

Entity Framework will be looking for a valid connection string in the app.config of the target project. In this case it can't find it.

The target project for EF Migrations is specified either by the -ProjectName option on the Add-Migration command, or it reverts to the default project as defined in the Package Manager Console.

Try setting the project name explicitly to the project that contains your DbContext.

In this case despite the fact I specified the default project and even tried the -ProjectName it was still using the Startup project to find the connection string. Changing this to an appropriate project (not tests) fixed my issue. Thanks

Collectives™ on Stack Overflow

Forceful reset of Entity Framework Migrations

1 Answer 1

1 Comment

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Related