>>Charles, you are so wrong ;-) Model first, not code first.
>>One of the nice things about the EF, even though I have backed off from it some, is that the choice is yours.
>
>Actually I do like the model first thing for a start from scratch project. The question is after that what? The Migration stuff may take care of updating schema on production data at some point but I think right now you have to reverse engineer out to classes that have the right migration metatdata etc and then go the other way when there are changes. I can do that with Redgate tools or DataDeploymentToolkit witout having to worry about it in the project.

My POV is that "model first" should be seen/interpreted conceptually ;-))
I "model" with the DD schema, viewing cardboard attempts as kindergarten attempts for people not used to relational db.
Defining a MVC/MVVM "model" as neccessary best practice first step (and I realize that a dozen different, but similar definitions exist)
IMHO borders on straw man technique to argue the point ;-)))
And I know that my leanings are not really impartial, but heyy!

>
>I think it will take a SQL Server specific 3rd party tool to do the schema sync the way I want it. Microsoft wants to make EF backend agnostic which is probably a good idea so each DB will have a niche for this kind of add on

Having burn marks I tend to disbelieve - somewhen marketing will decide it is better to shore up
and try to force others away from [linux,android,iOS]. Actually I am somewhat envious that you have
such a comfortable niche of whales accepting dotnet, as I view it technically to be ahead of java.

regards

thomas