General information
Category:
VFP Compiler for .NET
>
>
>>Again - what's in it for Microsoft to do this? Microsoft didn't give in to VB6 crowd (as they well shouldn't have) and they surely won't give in to the much, much smaller VFP community.
>
>But VB was not canceled. Not the same thing here.
>
>
>> But it's a hurdle that one gets over and then and only then does the benefit kick in.
>
>True and hope it's fast to learn!
>But many forget the small and mom and pop companies that don't have the thousands to invest in rewriting something that work for them.
>
>Like I mentioned in another thread, if they make a SP3 to support the next OS then I will make my peace(but won't like it in secret ;) )
As long as there is a company named Microsoft there will be some version of VB. When we go back to MainFrames (full cycle) it will be VB Cobal. :)
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only