The main usecase for the toolkit is replicating / packaging classic VFP functions into object calls.
If you're an "oldfashioned" FoxPro guy, you're used to commands and functions and you know them in and out. Thus you're tempted to have the same "ease of use" with NET. That's absolutely ok, but later on you will notice that the "real" NET way to deal with objects and their methods is notable more flexible. wOOdy -----Ursprüngliche Nachricht----- Von: ProFox <[email protected]> Im Auftrag von AndyHC Gesendet: Donnerstag, 22. November 2018 16:05 An: [email protected] Betreff: Re: Visual FoxPro Toolkit for .NET On 22-Nov-18 1:53 PM, Alan Bourke wrote: ... so give it, say, another 16 years and it could have caught up with Foxpro <g> [excessive quoting removed by server] _______________________________________________ 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/[email protected] ** 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.
