ef-migrations

In my application I enable Code First Migrations with some migrations, Also I use SQL Server Compact for integration test. When I run my tests, Entity Framework create an empty database and tries to run migration on that empty database and thrown The specified table does not exist. Based on this report I think usage of Migration in Entity Framework 6 has changed. I test all Database Initializer with Context.Database.Create(); but in all case tabale's never created. I don't know that this is EntityFramework's bug or not, but when I made rename the namespace of Migration Configuration class from

i installed EntityFramework.SqlMigrations NuGet Package and i get this error . it worked for me in the past and somehow, now it does not work. PM> update-database The term 'update-database' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:16 + update-database <<<< + CategoryInfo : ObjectNotFound: (update-database:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException Occurs with EF5 RTM, VS2012 RTM . I

I have a class that looks like this: [Table("Subscribers", Schema = "gligoran")] public class Subscriber { [Key] public string Email { get; set; } [Required] [DefaultValue(true)] public bool Enabled { get; set; } } When creating a migration to include this class I get: public partial class AddSubscriberClass : DbMigration { public override void Up() { CreateTable( "gligoran.Subscribers", c => new { Email = c.String(nullable: false, maxLength: 128), Enabled = c.Boolean(nullable: false), }) .PrimaryKey(t => t.Email); } public override void Down() { DropTable("gligoran.Subscribers"); } } I'd like

I'm currently using EF Code First 4.3 with migrations enabled, but automatic migrations disabled. My question is simple, is there a data annotations equivalent of the model configuration .WillCascadeOnDelete(false) I would like to decorate my class so that the foreign key relationships do NOT trigger a cascading delete. Code sample: public class Container { public int ContainerID { get; set; } public string Name { get; set; } public virtual ICollection<Output> Outputs { get; set; } } public class Output { public int ContainerID { get; set; } public virtual Container Container { get; set; }

TLDR; How do you add a full text index using Entity framework 5 coded migrations I'm having issues adding a full text index to a database using Entity framework migrations. It needs to be there from the start so I'm attempting modifying the InitialCreate migration that was automatically generated to add it. As there isn't a way to do it via the DbMigrations API I've resorted to running inline sql at the end of the 'Up' code. Sql("create fulltext catalog AppNameCatalog;"); Sql("create fulltext index on Document (Data type column Extension) key index [PK_dbo.Document] on AppNameCatalog;"); When

I have reverse-engineered the existing database to the code-first model. Some tables are to be kept but most are to be removed and completely re-architected for the new version. I delete some old classes and their mapping and add-migration. The migration looks like this: public override void Up() { DropForeignKey("dbo.Bingo_Review", "BingoID", "dbo.Bingo"); DropForeignKey("dbo.Bingo_Review_Text", "BingoReviewID", "dbo.Bingo_Review"); DropForeignKey("dbo.Bingo_Bonus", "BingoID", "dbo.Bingo"); DropForeignKey("dbo.Bingo_Bonus_Amount", "BingoBonusID", "dbo.Bingo_Bonus"); DropIndex("dbo.Bingo_Bonus

Background: We have a project that uses ef-migrations containing multiple (read ~60) migrations created over a long period of development. Naturally, some of these migrations also involve: dropping constraints 1 , 2 creating triggers All is unicorns and rainbows when we run Update-Database because each migration runs as a separate batch. But when creating SQL Scripts for these migrations using Update-Database -Script we encountered a few issues as described below: Problem 1: When dropping multiple constraints across multiple migration files, the script generated by EF tends to re-declare