>>>>What are the pros and cons of FoxISAPI vs WebConnect vs FoxWeb vs AFP? Does anyone have any hard information? I'm sure that there are lots of opinions - what are they?
>>
>>>So far you've gotten several "Use Web Connect" answers. I'll take a different approach. If you use ASP and connect to COM components running in MTS/COM+, you'll learn things that are more usable at future jobs.
>>
>>I have been mulling this over as well. Would using using a product like WebConnect retard my learning of MTS/COM+?
>
>WebConnect does not use MTS/COM+. It uses ISAPI. I can't say if it would retard your learning, but IMO, I can't see where it would help.

Neither does ASP until you explicitly use it. If you want to use MTS/COM you certainly can do that in exactly the same way you can in ASP pages, although that'll obviously bring up the question why bother...

MTS/COM+ really has nothing to do with ASP anyway. COM+ services other than scalability (which MTS/COM+ sucks at for most applications - there have been a number of articles on this recently on the DevX/VBPJ) don't require any specific platform to run. COM+ is really about service like queued components, COM+ events, distributed transactions etc. all of which are not directly applicable to Web applications and won't be any easier or harder in either inside of VFP or ASP.

The final counter argument is that with .Net coming COM is going to be downplayed considerably because you won't be running COM objects but managed code in the CLR. Once again there's no real benefit coming from one platform or the other because .Net will change the way *everything* is done using CLR objects for most functionaltity, which both your business objects and ASP+ script code will consume.


+++ Rick ---