Question

I have taken over an existing project written beautifully in SQL with many useful and clean stored procedures.

I was told as a bonus that I should make several additions and ideally re-write the code in MVC.

I have so far have generated my datamodels and created function imports and complex types.

It has been fun, but now I am feeling bad that I never used a true Entity Framework Code First scenario. I would of had a more succinct code, smoother validation and more MVC purist friends.

What do you think?
What would you have done?
I have a theory that there will be significant changes ahead anyhow to the Entity Framework Code First scenario, so pure SQL is a safer choice.

Thanks for your advice!

Answer 1

Code first makes more sense when prototyping or doing some kind of RAD development. Since you already had your SQL data model developed, there is no benefit to taking a code-first approach. You can develop clean code either way.