>I haven't found web programming with ASP.NET orders of magnitude easier than implementing a vfp web application with a VFP mtdll.

Maybe not an order of magnitude, but it's definitely an easier model. The mere fact that you can debug your code inline and you get a decent code editor where Intellisense actually works correctly is worth the price of admission. Beyond the learning curve for .NET lies more productivity.

But the biggest issue remains the deployment. Regardless of which route you take, VFP requires some configuration and extra installation. With ASP.NET if I update my applications I copy files to the server - that's it. The first time I need to create virtual, but after that it's true XCOPY deployment, nor are any special rights required for the code to run.

I'm not saying you can't make this easy with Fox, but it is a lot more work.

For example, in my Fox Web Connection apps on the server I have a build routine that automatically FTP's the updated EXE to the server and hotswaps it while the server is running. The whole process takes about 2 minutes and hte Web server is never down, and the application is unresponsive for about 2-3 seconds. The code that does this is about 20 lines most of which deals with authentication issues. But you have to know how to do this (although we actually ship instructions and examples exactly on doing this - but of course few actually read it!)