Hi Francisco,

Personally, I'm not sweating Longhorn right now.
Why? It won't even be RELEASED for *three more years*.

We'll have --several-- versions of VFP between now and then. That's more than enough time to focus on providing our employers/customers real-world solutions using one of the best tools available for that purpose, and FAR more than enough time for the VFP team at MS to build all sorts of new features and capabilities into the product. I would imagine that the .NET classes will also have several versions between now and then.

And, when Longhorn arrives, it's STILL going to take at least a year before most corporate clients migrate to the product (and probably a lot longer than that -- how many small to medium-size corporations are *still* using Windows 2000, both the server AND workstation products??) That's assuming, of course, that MS doesn't slip the delivery date on Longhorn (which, of course, NEVER happens in our business, right?) (bg)

So, that's at minimum four years before I've really got to worry. That's forever in this industry. Lots of water can pass under the bridge (and lots of solutions can be provided) in that length of time.

Just my USD$0.02 worth...


>Hello everybody,
>
>I'm a VFP Fan.
>I'm at the PDC right now.
>I just saw what will the new Windows Longhorn applications look alike. And what the new technologies (Avalon, Indigo, Smartdevices development) enable and how to use them in .NETR managed code.
>Of course there will be a complete .NET class libraries to work with all the new Longhorn and Avalon (the visual presentation layer) features.
>
>My question is:
>
>How do you think we, in VFP will be able to keep up with this evolution ?
>
>The way I see it, the .NET world gets to use all the novelties of the platforms and other technologies but we don't.
>
>All comments will be apreciated
>
>Thanks