>
>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.
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
Charles Hankey
Though a good deal is too strange to be believed, nothing is too strange to have happened.
- Thomas Hardy
Half the harm that is done in this world is due to people who want to feel important. They don't mean to do harm-- but the harm does not interest them. Or they do not see it, or they justify it because they are absorbed in the endless struggle to think well of themselves.
-- T. S. Eliot
Democracy is two wolves and a sheep voting on what to have for lunch.
Liberty is a well-armed sheep contesting the vote.
- Ben Franklin
Pardon him, Theodotus. He is a barbarian, and thinks that the customs of his tribe and island are the laws of nature.
