I've had several problems with FOXISAPI. It can be hard to install, sometimes it just doesn't seem to work,debugging doesn't work, little or no support from Microsoft or users. And I think you have to use DCOM to set up the servers in FOXISAPI which is kind of a pain. You'll find these things out if you start using it.
This is one of the reasons that I created a free web framework that works with VFP mtdlls and ASp/ASP.NET. The goal was to make all of this stuff work as smoothly as possible with the least hassle and at the best scalability/performance...
>I'm afraid that as I haven't actually used WebConnect I have really misunderstood things (probably because WestWind still has quite many articles on their site that explain how to use FoxISAPI).
>
>I need to build a desktop application that uses data over Internet. If I were to build a system with browser based UI then I'd understand that using WebConnect is the best choise.
>
>My question is why should I buy WebConnect instead of using FoxISAPI. Even if FoxISAPI is not supported anymore - it should still be usable? The problem is that I don't want to go for WebConnect unless I'm absolutely certain that it offers significant benefit.
>
>DCOM or COM+ is just another possible solution that came to my mind. I could just put some application logic on server and use DCOM to exchange data.
>
>The last solution does seem cheaper but are there any hidden dangers? (e.g slower performance)
>
>Thanks!