Hi Claude,

>Similar, but the ASP.NET web apps are still dlls, not exes, built with C# or VB.net. The ASP.NET setup also seems similar to how vfp mtdlls work inside of mts which is a .EXE, I believe.

ASP.NET applications are assemblies which aren't even native DLLs, but more like VFP's APP files. In any case, I still fail to see the difference between:

a) Having a AFP.8.EXE that loads the VFP8R.DLL and services requests (AFP EXE mode), and

b) Having an ASPNET_WP.EXE that loads a MSCOREE.DLL that loads an ASP.NET assembly DLL (ASP.NET page), and

c) Having an ASPNET_WP.EXE that loads a MSCOREE.DLL that loads an ASP.NET assembly DLL that loads a VFP DLL that loads the VFP8T.DLL (ActiveVFP with ASP.NET host), and

d) Having an MTS.EXE that loads a VFP DLL that loads the VFP8T.DLL (ActiveVFP with MTS/COM+)

What makes one of these approaches superior to others?