Do VS Database and Entity Framework projects work together?

Question

I have always been intrigued by Visual Studio Database Projects, and although they seem quite capable, I have never used them to a large extent outside of the simplified work involved in proving the concept. I want to try this for a new project, and I am also interested in using the EF layer on top of it, but in past test projects this has attracted some decent effort.

I'm curious: Visual Studio is ripe for product integration to support a single workflow that builds a database project, builds an EF layer on top of it, and finally creates code without intermediate steps?

We are a small team, and we do not have specialized SQL developers, and our main task is to bring the database to Visual Studio and get it under source control (TFS) and achieve strong integration between the final ones at the end. We are interested in developing into EF and will probably start simply by considering it as a simple ORM tool, if possible.

Has anyone really done this to provide an understanding of the process?

Answer 1

We used VS2014, the tool seemed almost the same and an early version. I do not think that big changes have occurred over the years.

We have an EDMX model and a DB project in solution. This means that you need to update the db project. But this is easy to do, you just publish EDMX in the local field / goal. Then you can import the changes comparing the local project with the project.

So, you can still have a DB design with a model AND use the database project to deploy the changes to the Dev / Stage / Live blocks And you can also publish with automatic deployment.

There is an option post post scripts in the db project where you can use it to get data about the seed. There is also a preliminary assembly where you can manipulate db if you need to change the structure and types of field types when the data is on real db.

The schema comparison tool is pretty good in Visual Studio. You can compare a database with a database, a database with a project, or with a schema file so that either