Nope, that's not what I'm saying. Just as EF is not the end-all cure, neither are SPROCs. Choose which one is best for the job.

If something comes from the Migrations namespace, I'd say that's what it's for. It may work fine now in production, but we don't know if that will change in the future. You may not find out it's changed until you're screwed.

My response is that Julie knows more about EF than just about anyone. Follow her advice.


>I really don't understand what you all are proposing. Are you saying to use SPROCs instead of EF? So, your responses don't help me at all in convincing these people not to use EF's AddOrUpdate which comes from the Migrations namespace.
>
>Using SPROCs: That's not going to happen. People here will not permit us to use SPROCs even when I've made a case to use them instead of very complicated LINQ.
>
>Also, SQL Profiler shows that the SQL generated by EF 6.02 or whatever is the latest is not using Merge. It's using either an Insert or an Update.