Christof:
Interesting approach. What happens if a future Windows version breaks VFP runtime, i.e., VFP runtime support won't be available any longer? What about other platforms like Linux (running Wine for example) -- isn't VFP runtime contractually limited to Windows only?
How long do you think it will realistically take for you to have your system close to 100% compatible with VFP -- IOW, you can just point at your VFP app from .NET and run it like always?
Pertti
>Hi Tracy,
>
>> How will it differ from etechnologia's stuff?
>
>The approach is different...
>
>Guineu is basically a runtime library for VFP for existing code. My focus is mainly on preserving investments in existing FoxPro code, because that's what my clients spend over the last 20 years writing. I simply don't like the idea of throwing working stuff away just because it's not cool enough any more. The fact that Guineu is written in C# isn't that important. As a developer you are using VFP to create applications just like before. All you change is the runtime to execute your app on, for instance, a PDA. You don't need to learn the .NET framework or another language to write code.
>
>Etecnologia, on the other hand, creates a VFP based .NET language including (optional) strong typing, enums, constructors, and the like. To get the most out of their solution, you need/should learn the .NET framework.
>
>In the end the goal of both tools is to execute FoxPro code giving you a choice to pick the tool that suits you better.