If you’re using Code First and have (an) existing Migration script(s) and are trying to overwrite a change (i.e. renaming a column) that has since been deleted, then you’ll get that error output. Simplest way is to delete the migration script, Add-Migration via NuGet, and then update the database.
I found the solution here. In short, edit your csproj file, and add to your PropertyGroup section the following entry: <GenerateRuntimeConfigurationFiles>True</GenerateRuntimeConfigurationFiles>
1- Make sure to set your web project as Set as Startup Project 2- In Package Manager Console, set your data access layer (if any) as a default project 3- Then run the command again
I noticed in visual studio, going to SQL menu, Transact-SQL Editor, New Query… gave a dialog about the tools not working with the server installed. Installing SQL Server Data Tools – December 2012 update (Sql Server Data Tools) fixed the problem
The fact that the Seed method ran only when the database changed was quite limiting for the database initializers that shipped in EF 4.1. It was limiting because sometimes you needed to update seed data without changing the database, but to make that happen you had to artificially make it seem like the database had … Read more
Oh wow, nevermind. I’m dumb. In the Nuget package manager console there is a dropdown menu at the top labeled “Default Project:”. Make sure you set that to the project you want to run the command against. Hopefully this helps someone else avoid my embarrassing mistake.
update-database -verbose doesn’t work because your model has been changed after your data table already existed. First, make sure there are no changes to the UserProfile class. Then, run: Add-Migration InitialMigrations -IgnoreChanges This should generate a blank “InitialMigration” file. Now, add any desired changes to the UserProfile class. Once changes are added, run the update … Read more
When I have fixed data that I want to insert with a migration, I put the inserts directly in the Up() migration using calls to Sql(“Insert …”). See the note halfway down this page: how to insert fixed data You prevent duplicates in the Seed method by calling the AddOrUpdate overload that takes an identifier … Read more
On the package manager console type: Get-Help Update-Database Relevant part: Update-Database [-SourceMigration <String>] [-TargetMigration <String>] [-Script] [-Force] [-ProjectName <String>] [-StartUpProjectName <String>] [-ConfigurationTypeName <String>] [-ConnectionStringName <String>] [<Com monParameters>] So you can do a Update-Database -ConnectionStringName “MyConnectionString” and it should work like a charm. You also have a MigrateDatabaseToLatestVersion database initializer, if you set it (via Database.SetInitializer()), … Read more
Answering your first question. Create a Migration by running add-migration SeedOnly Clear out all Up() and Down() code generated if there was any pending changes public partial class SeedOnly : DbMigration { public override void Up() { } public override void Down() { } } Then you can Target a Specific Migration by running update-database … Read more