I wasn't advocating any of the alternatives - just pointing out the WCF handles a lot more binding options than HTTP.....

>VFP could use MSMQ, but that would add lots of complexity.
>
>>Hmm. Tcp, NamedPipes, MSMQ ?
>>
>>> and VFP doesn't play well there. I would not look at a hybrid solution.
>>But there I would agree....
>>
>>>If you need to migrate your application to .Net, I'd look at migrating by functionality (vertically) rather than by tier (horizontally). Look at the book "Brownfield Development in .Net" for ideas on how to go about this.
>>>
>>>>Hello
>>>>Has anybody of you try with vfp in ntier solution in .net .Being vfp a middle tier or presentation tier?
>>>>in COM+ or webservice or WCF?
>>>>Can you tell me your experiences about it?it happened any problem while running?
>>>>Do anybody of you have any sample of this to check out?
>>>>Thank you in advance