Asp.net-mvc – Entity Framework 6.0 Code First Migrations to Azure SQL DB not working.

asp.net-mvcazureentity-frameworkentity-framework-migrations

I am trying to create an ASP.NET MVC site loosely based on this tutorial.
http://www.windowsazure.com/en-us/develop/net/tutorials/web-site-with-sql-database/

I am using VS2013 preview which gave me the option to create an ASP.NET MVC 5 site. Also, using the following packages:

EntityFramework 6.0.0-rc1

Microsoft.AspNet.Identity.Core" 1.0.0-alpha1

Microsoft.AspNet.Identity.EntityFramework 1.0.0-alpha1

After configuring a website and associating it with a database in Azure, I proceeded to run the following commands in the package manager console:

enable-migrations -ContextTypeName IdentityDbContext

add-migration Initial

When I published to Azure with the database specified and the "Execute Code First Migrations" checkbox checked, the site deployed properly, but after inspecting my DB, the migrations didn't run. My migrations had been successful previously on a site with ASP.Net MVC 4 and EF 5.0.

I would guess the problem is that EF 6 is ignoring the connection string that is set during publishing, but I cannot understand why.

Any help would be appreciated. Thank you.

Best Answer

This guide looks comprehensive: http://www.asp.net/mvc/tutorials/getting-started-with-ef-using-mvc/migrations-and-deployment-with-the-entity-framework-in-an-asp-net-mvc-application

The key part being "Execute Code First Migrations (runs on application start)"

I hope that helps.

Related Solutions

.net – Entity Framework vs LINQ to SQL

LINQ to SQL only supports 1 to 1 mapping of database tables, views, sprocs and functions available in Microsoft SQL Server. It's a great API to use for quick data access construction to relatively well designed SQL Server databases. LINQ2SQL was first released with C# 3.0 and .Net Framework 3.5.

LINQ to Entities (ADO.Net Entity Framework) is an ORM (Object Relational Mapper) API which allows for a broad definition of object domain models and their relationships to many different ADO.Net data providers. As such, you can mix and match a number of different database vendors, application servers or protocols to design an aggregated mash-up of objects which are constructed from a variety of tables, sources, services, etc. ADO.Net Framework was released with the .Net Framework 3.5 SP1.

This is a good introductory article on MSDN: Introducing LINQ to Relational Data

Entity-framework – How to view the SQL generated by the Entity Framework

For those using Entity Framework 6 and up, if you want to view the output SQL in Visual Studio (like I did) you have to use the new logging/interception functionality.

Adding the following line will spit out the generated SQL (along with additional execution-related details) in the Visual Studio output panel:

using (MyDatabaseEntities context = new MyDatabaseEntities())
{
    context.Database.Log = s => System.Diagnostics.Debug.WriteLine(s);
    // query the database using EF here.
}

More information about logging in EF6 in this nifty blog series: http://blog.oneunicorn.com/2013/05/08/ef6-sql-logging-part-1-simple-logging/

Note: Make sure you are running your project in DEBUG mode.

Related Topic