Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Last version
Message
 
To
14/01/2008 09:48:24
General information
Forum:
Visual FoxPro
Category:
VFPX/Sedna
Title:
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Vista
Network:
Windows 2003 Server
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01281540
Message ID:
01281696
Views:
6
Hi Sylvain:

We are a real .NET language ;-). The things you can do in other .NET Languages you can do it now in FoxPro compiled to .NET. Think Winforms, ASP.NET, Linux, OSX, Mobile Devices, you can have it in FoxPro code now.

And you have the big bonus and the reason of our effort: VFP powerful Data Access. VFP has years of fine tuning its language semantics and runtime to work with Data and to have that power in .NET is amazing, and it gives you a big edge over any other .NET programmer. You can build better data solutions in far less time and code in VFP than in the other .NET languages.

The other mainstream .NET Languages are nowhere near, neither on its VB9 or C# 3 incarnations, to what VFP can do with Data. Not to mention the VFP'S more powerful OOP model, dynamic capabilities, have you hear that now the "dynamic languages are hot"?, well, VFP was cool dynamic even before that phrase were coined.

And now you can move to your own pace to .NET, it is great to have a big Class Library as the .NET Framework for your use in your VFP apps. But .NET Data Access and Binding is a pain as the other comments in this thread show.

And we are adding new functionality to the FoxPro language / runtime, while still remaining fully compatible check our site at www.etecnologia.net. The introduced changes give you more power and are evolutionaries. Change is good when it is evolutionary, to improve; but to change when it means "backward steps" is involution, something most people is likely to avoid.


>AFAIK, they won't add any new functionality other than offering the possibility of running in .NET. They may add a couple of years to the life of VFP applications, but that won't prevent VFP from being obsolete.
>
>I'm still amazed to see developers so attached to a given tool that they won't even try to learn/use anything else. It's a little bit like a construction worker who is the master of the hammer. Everything look like a nail to him and he won't let go of his hammer for nothing. Sometime a screwdriver may be a better option to work with a screw.
>
>If you want your application to run in .NET, why don't you use a real .NET language?
>
>>It is the last version from Microsoft.
>>
>>Let's hope Guineu and etecnologia both make it. Either of them 'deserves' the name VFP10 to me.
Previous
Reply
Map
View

Click here to load this message in the networking platform