Deploy Entity Framework Code First

Question

I guess I should have thought of this before I started my project but I have successfully built and tested a mini application using the code-first approach and I am ready to deploy it to a production web server.

I have moved the folder to my staging server and everything works well. I am just curious if there is a suggested deployment strategy?

If I make a change to the application I don't want to lose all the data if the application is restarted.

Should I just generate the DB scripts from the code-first project and then move it to my server that way?

Any tips and guide links would be useful.

Thanks.

Ladislav Mrnka · Accepted Answer · 2011-04-06 22:50:45Z

5

Actually database initializer is only for development. Deploying such code to production is the best way to get some troubles. Code-first currently doesn't have any approach for database evolution so you must manually build change scripts to your database after new version. The easiest approach is using Database tools in VS Studio 2010 Premium and Ultimate. If you will have a database with the old schema and a database with the new schema and VS will prepare change script for you.

answered Apr 6, 2011 at 22:50

Ladislav Mrnka

365k60 gold badges666 silver badges673 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

KidCoke Over a year ago

Pardon my ignorance. But could you outline the steps I should take to move this project to my production server?

billy Over a year ago

I too would like more info, @Ladislav

wil Over a year ago

I would also like more info! There are restrictions locally such as the 4k string limit (I need max for production)... so, how do I create/get the final schema?

adimauro · Accepted Answer · 2011-09-13 15:03:05Z

1

Here are the steps I follow.

Comment out any Initialization strategy I'm using.
Generate the database scripts for schema + data for all the tables EXCEPT the EdmMetadata table and run them on the web server. (Of course, if it's a production server, BE CAREFUL about this step. In my case, during development, the data in production and development are identical.)
Commit my solution to subversion which then triggers TeamCity to build, test, and deploy to the web server (of course, you will have your own method for this step, but somehow deploy the website to the web server).
You're all done!

The Initializer and the EdmMetadata tables are needed for development only.

answered Sep 13, 2011 at 15:03

adimauro

3331 silver badge12 bronze badges

2 Comments

kingdango Over a year ago

Yes, this is essentially the manual way to do what a Visual Studio Database Project does automatically for you. kingdango.com/blog/2011/12/…

Nathan Koop Over a year ago

NOTE: you can use preprocessor directives to automatically remove the SetInitializer msdn.microsoft.com/en-us/library/4y6tbswk.aspx

Collectives™ on Stack Overflow

Deploy Entity Framework Code First

2 Answers 2

3 Comments

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

3 Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related