WCF can be COM-enabled. I have an article on my web site that shows how. Also, if you lean toward web services, go with WCF there over ASMX.

>I'm looking for the pros and cons of each communication options between a VFP front-end and a C# middle-end (SQL Server as a back-end).
>
>From what I could find, there's 3 way to communicate:
>
>- .NET as a COM
>- Web services
>- eTecnologia .NET Extender for VFP
>
>I've read Rick Strahl article "Using .NET Components via COM from Visual FoxPro (or other COM client)" (http://www.west-wind.com/presentations/VfpDotNetInterop/DotNetFromVFP.asp) and he offer some good advices on using .NET as COM from VFP.
>
>I thought at first that web services would be the prefered way because it's everywhere, but in his other article ".NET Interop for Visual FoxPro Applications" (http://www.west-wind.com/presentations/VfpDotNetInterop/vfpDotNetInterop.htm), he says I believe that Web Services as a pure Interop technology are not the best mechanism to pass data or logic around.
>
>eTecnologia .NET Extender for VFP look good, but I wonder if it would do the job.
>
>What do you think? Which one would you chose and why? Did I miss any other way to communicate?
>
>TIA