@carlospinedag I agree; I am also not a huge fan of Code First. Model first is more natural for me; helps keep the database design ownership to select few! Code First makes it difficult to keep control over your db model. I also don't like the idea of C# code driving my database design; I would rather design my database model, generate the differentiating SQL, provide is to the developers so that they could code their stuff on top of it.
@romiller, currently we are working on a multi-year Azure SQL Database / MVC / Web API / EF 6.1 project that uses model first approach. Can you please provide any guidance or tips and tricks for us to avoid making any mistakes that might cost us time/money while upgrading from EF 6.1 to EF7 in the future? Will there be no tooling in EF7 to generate classes/context from the model?