EF and WCF are different animals with different purposes.

>Disclaimer - what I'm about to say is personal opinion.
>
>While I liked .NET remoting, I wound up liking WCF much better. In that case, I thought MS hit the nail on the head....they hit the proverbial home run.
>
>On the other hand, I never thought EF was an example of taking what was previously there and hitting a home run.
>
>With WCF, I saw compelling reasons to change. It was better.
>
>With EF, I think it's more "different" than better.
>
>Again, that is personal opinion. If I were forced to use EF on a project, I wouldn't fight it...I'd play along.