A quick hack I use to be able to quickly find a value in my Seed method is simply to throw an exception with a value I care about, e.g. throw new Exception(yourValue); This errors out the Seed, but my exception/value appears in my package manager console.
In the configuration class constructor add this line: this.MigrationsDirectory = “DirOne\\DirTwo”; The namespace will continue to be set as the namespace of the configuration class itself. To change this add this line (also in the configuration constructor): this.MigrationsNamespace = “MyApp.DirOne.DirTwo”;
The smartest way is probably to not alter types. If you need to do this, I’d suggest you to do the following steps: Add a new column with your new type Use Sql() to take over the data from the original column using an update statement Remove the old column Rename the new column This … Read more
I had a similar problem where a new migration was not being found, and so update-database was giving me the following error no matter what I did: Unable to update database to match the current model because there are pending changes and automatic migration is disabled. Either write the pending model changes to a code-based … Read more
We support stored procedures in our Entity Framework Code First Migrations. Our approach is to create some folder to hold the .sql files (~/Sql/ for example). Create .sql files in the folder for both creating and dropping the stored procedure. E.g. Create_sp_DoSomething.sql and Drop_sp_DoSomething. Because the SQL runs in a batch and CREATE PROCEDURE.. must … Read more
You need to add a blank “merge” migration that will reset the snapshot of the latest migration in the .resx file. Do this using the IgnoreChanges switch: Add-Migration <migration name> -IgnoreChanges See here for an explanation
Consider reading this nice article from Rick Strahl : https://weblog.west-wind.com/posts/2016/jan/13/resetting-entity-framework-migrations-to-a-clean-slate Basically the solution is not trivial and needs more than just reseting all the migrations into one because you have two scenarios that needs to fit in ONE migration class: Create a new database => the migration class should contain every table creation My database … Read more
sometimes you need to change the current directory in console/terminal eg: PM> cd E:\Projects\CrossTest\ PM> dotnet ef migrations add InitialMigration and Align your package versions. Either use preview1 packages or preview2. Mix of those are not supported.
You have a default constraint on your column. You need to first drop the constraint, then alter your column. public override void Up() { Sql(“ALTER TABLE dbo.Received DROP CONSTRAINT DF_Receiv_FromN__25869641”); AlterColumn(“dbo.Received”, “FromNo”, c => c.String()); AlterColumn(“dbo.Received”, “ToNo”, c => c.String()); AlterColumn(“dbo.Received”, “TicketNo”, c => c.String()); } You will probably have to drop the default constraints … Read more
The Up method upgrades your database from its current state (represented by your previous migration) to the state expected by your current code migration. The Down method does the reverse operation – it removes all the changes from the current migration and reverts database to the state expected by the previous migration. It’s like installing … Read more