Resetting Entity Framework Migrations to a clean Slate

Posted by: Rick Strahls WebLog, on 14 Jan 2016 | View original | Bookmarked: 0 time(s)

Not sure if this is a common occurrence, but I've had a number of occasions where Entity Framework migrations have left the state of migrations in an unusable state. Usually this happens after a large number of migrations have been applied and I get stuck to where I can't update a database with new migrations or roll back. It simply won't go. There are a number of hacks you can try to fix bonked migrations, but to be honest more often than not those simply don't work. So what do you do? I've found...

Category: XSD | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 1 | Hits: 0

Similar Posts

  • Resetting Entity Framework Migrations to a clean Slate more
  • Talking Points: ADO.NET Entity Framework more
  • Best approach for teaching first exposure to Entity Framework more
  • More on Foreign Keys in EF more
  • Overloading Entity Framework Methods: More GetObjectStateEntries more
  • WPF Series: IFrameworkElement - the missing interface more
  • Delete Stored Procs and Navigations in the Entity Data Model more
  • Sneak Peek at the EntityDataSource Control more
  • Inheritance and the Entity Framework more
  • Choosing LINQ to Entities vs Entity SQL vs. EntityClient more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD