Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
It seems that VFPers are not interested in .NET/CLR yet
Message
De
04/10/2000 07:23:13
Walter Meester
HoogkarspelPays-Bas
 
 
À
04/10/2000 06:38:38
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00423332
Message ID:
00424605
Vues:
16
Hi Ed,

>>In addition to David, To me it's like we can do all the things we can do in VB we can do with C++. On only some points (features that closely related to the CLR) we have to use some workarrounds. As said before, the whole .NET things is much more than only CLR. VFP can fully participate in .NET excluding compiling to the CLR. AFIAK, this only a small part of the whole, which can be (easely ??) bypassed.

>That's interesting; I take it you know more than the MS people about this. As of last week, the MS team indicated that VFP will not be a full participant in the managed code playground.

Isn't this what I said (Excluding CLR) ??

>While from an application programmer POV it may not matter, there are fundamental differences between languages that emit IL via a JIT compiler, and VFP's interpretive environment

Agreed, but on the whole, how serious is this ?

>There will be circumstances that will rule out VFP as the principal tool for developing certain types of apps. VFP still won't be able to publish an entrypoint for callbacks from what I've seen and read.

Does this have anything to do with compiling to the CLR or does it show the shortcummings of VFP API/COM handling. If the latter, maybe the VFP team can fill this hole. Do you have any insights what kind of apps will rule out VFP ?

>>So we are debating only a small part of .NET where we cannot have direct support but might have via COM services etc..

>No, people are speculating wildly and pointlessly on this

Are you telling that CLR is not a small part of .NET ?

>, in spite of being told the product is a couple of months from entering beta, perhaps a year from a real product, and a new OS in there as well. It makes much more sense to play with the Tech Previews, both VFP and the PDC release, and keep on top of the MS site. Even the development team at MS isn't sure where things are going; perhaps a little empirical observation and waiting is in order.

You're right. Since the product is still in development, we cannot set a course for VFP unless it's clear what .NET means, how it works, and how VFP fits in this story.

Walter,
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform