>>>It would? Maybe there is something fundamental I am missing about eTecnologia's product. I thought it was a tool to compile VFP code to .NET. (Is that incorrect?) I don't see how that makes VFP any less deadend.
>>
>>Is this your personal attitude as a developer?
>>
>
>I'm not sure I understand the question. Can you please elaborate so I know I'm answering the right question?

I think what I am getting at here is when you look at FoxPro + .NET as a developer does it seem just as much a deadend as FoxPro alone?

There is also the way that a client would look at the combination. I wanted to make a distinction between the marketabilty and your personal judgement.

I don't know .NET so I'm basically ignorant here. My assumption is that a FoxPro app running under .NET would have more future possiblities.

For instance, you compile VFP to .NET IL. (Big if :) Could you bind that to a new module written in VB or C#?

This is how a similar situation looks to the IronPython guys:

What is IronPython?
IronPython is a new implementation of the Python language targeting the Common Language Runtime (CLR). It compiles python programs into bytecode (IL) that will run on either Microsoft's .NET or the Open Source Mono platform. IronPython includes an interactive interpreter and transparent on-the-fly compilation of source files just like standard Python. In addition, IronPython supports static compilation of Python code to produce static executables (.exe's) that can be run directly or static libraries (.dll's) that can be called from other CLR languages.

The CLR is designed to be a target platform for multiple programming languages and to provide a common type system that can enable these languages to seamlessly interoperate with each other. IronPython adds Python to this mix of languages allowing Python code to easily use and be used from the wide variety of other languages that support the CLR.
http://www.python.org/community/pycon/dc2004/papers/9/

Peter