Even if it's not portable, it's still easier than writing completely from scratch in a brand new language. I've web-enabled many .vfp. .GUI. applications this way. Although not completely trivial to do , a lot of the code logic can remain the same.

Performance in .NET is more than likely better, but, not by any great degree in most web applications unless we're talking something very large like an Ebay or Amazon where the benefits probably would be seen in a pure .NET environment.

>This assumes the code is in a portable state. Very rare is the case that a >
>simple recompile into a dll will do the trick.
>Why do you conclude the performance in .NET cannot be better? Fox's only >speed advantage rests with local data. That advantage evaporates in the >web/distributed computing arena.

>
>>From the VFP 8 FAQ page at http://msdn.microsoft.com/vfoxpro/productinfo/faq/default.aspx:
>>"Q. Can I use Visual FoxPro to build Web applications?
>>A. Visual FoxPro COM components can be used with Internet Information Services (IIS) to build high-powered Internet database applications. This is because Visual FoxPro components can be called from Active Server Pages (ASP). Visual FoxPro is compatible with ASP but works even better in conjunction with the more modern ASP.NET. The components will retrieve and manipulate data, and will build some of the HTML returned to the user.
>>Q. Why would I build a component in Visual FoxPro when I can build the same component in Microsoft Visual Basic or Microsoft Visual C++?
>>A. Visual FoxPro components are extremely fast, thanks to the data-centric language of Visual FoxPro and its ability to quickly retrieve and manipulate data. Further, Visual FoxPro can build character strings very swiftly. A Visual FoxPro component that works with data and returns HTML will, therefore, be very fast.
>>Visual FoxPro also has object-oriented programming capabilities, including inheritance. This provides a high degree of reuse across applications. A Visual FoxPro developer can create a set of classes that includes the core functionality of a Web database component, so that code will not need to be rewritten each time a component is needed in a Web application. The developer can simply create a component that inherits the base functionality, and then add application-specific code to it.
>>Finally, building COM components in Visual FoxPro is an excellent way to reuse existing code. Code that is already written and tested can be built into a component, rather than being recreated in another language.
>>"
>>>our company is now in the process of rewriting our VFP7 application to use SQl as backend. We're thinking about a Web aplication since we have customers in USA and all around our country. We are taking some trainings of SQl sever too, we heard about N-tier app and we are wondering: is VFP8 the best for this kind of thing? is .Net? what do you guys think according to your experience?