> what benefit could there possibly be? What ROI? Exactly. Especially since Microsoft are intent on moving their development tools into an open source, cross-platform, cloud-friendly paradigm. Why would you re-engineer the functionality to work with DBF when everything going forward will talk to a database server directly or through an API? So when you strip away that, and by extension the ancillary parts like the report designer what are you left with? A syntax, essentially. Which (with all the legacy crap like @ ... SAY removed) a third-party could produce as a .NET language if there was demand.
In terms of future proofing VFP I'd be happy with MS providing the same 'it just works' status for the runtimes that the VB6 ones have. -- Alan Bourke alanpbourke (at) fastmail (dot) fm _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/1457525112.3225739.544056666.0b1b1...@webmail.messagingengine.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
