>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.

Craig,

I fully agree with you and Julie. But, I'm working with some other guys with more experience than myself and am in a situation where my book learning, blog reading, and Pluralsight videos and such are pretty much laughed at.

And, finally, these guys have never even heard of Julie.

Again, the Migrations namespace, IMO, is a dead giveaway that it should not be used.
Add that to the fact that SQL Profiler shows it doing a SELECT query against the table before sending in an insert or an update is a dead giveaway that the AddOrUpdate doesn't care much about performance.