Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Should VFP Become dotNet?
Message
De
27/06/2004 08:46:40
Dorin Vasilescu
ALL Trans Romania
Arad, Roumanie
 
 
À
25/06/2004 10:08:04
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00915955
Message ID:
00917697
Vues:
14
This is not what I meant
I wanted to say that I believe is possible to port C++ code to NET managed code and still to have the same VFP, but running on that platform, interpreting xBase code. I'm not talking about winforms,NET datasets or COM interop. But I'm sure that such thing is never going to happen.

If not, at least the engine, capable to talk DIRECTLY with data, without the need to load everything in memory before you can do something, in a form of VFPDataEngine namespace or something. I'm sure that will be a lot of people making a good use of it, instead using external engines (Jet,MSDE,etc)

>Dorin,
>
>>I don't believe that VFP cannot be ported to NET platform as it is. I don't believe that the engine cannot be ported also (exists already Codebase NET). I've seen entire IDEs built on NET platform, or games. Why an interpreted xBase language cannot be built/ported? (I bet that runtimes will be very small)
>
>If you have some time to spare, you could play with the idea of talking to the VFP API through C++ or instantiating a VFP Application object from inside .NET (through COM interop) and calling its DoCmd, Eval and SetVar functions to do what you want. Of course, you would not be able to directly tie in your cursors in that automation object to your .NET UI, so what would that buy you that just calling a fully programmed VFP COM object would not?
>
>It would be like remotely driving a car by giving instructions to someone over the phone. You might accomplish something, but you might not like the result. :-)
>
>You could, of course, have your remote manipulation of the VFP application object use XMLAdapter to convert your result cursor(s) into .NET DataSets and return those over the COM boundary (in theory -- I haven't tested this), so once you wrote a .NET IDE replatement or plug-in or alternative IDE to handle VFp syntax in the .NET IDE and then you wrote a .NET compiler to turn the VFp data access syntax into calls to the VFP application object, then you would have only a few thousand other problems to solve.
>
>But, yes, I'm sure it could be done. Some very smart people have probably spent quite a good many brainstorming sessions on the subject, but maybe some enterprising person or team of people will step up and just do it.
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform