Mike, Due to security reasons, it cannot be a web or cloud based app. So that limits some of the choices. Also, it is for one of those markets where Windows desktops prevail almost universally. So there is limited need for cross platform support.
We are planning on a long term conversion, with our goal being to have the entire application suite converted by the 2015. This is not a trivial application. So we will continue to support/enhance the VFP products. But we are running into IT departments that are making roadblocks to new sales because of the 2015 deadline. What other languages would you recommend, now that you know more? Thanks, Fletcher Fletcher Johnson [email protected] 408-946-0960 - Work 501-421-9629 - Fax -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of MB Software Solutions, LLC Sent: Wednesday, June 22, 2011 1:07 PM To: ProFox Email List Subject: Re: [NF] Questions on migrating VFP app On 6/22/2011 3:58 PM, Fletcher Johnson wrote: > Hi all, > > I am working with a new company that has a successful VFP app that > they need to convert to .NET as MS will be cancelling support for VFP > soon and the customers IT departments are getting nervous. So I have > been asked to help with a rewrite. > > I am sure there have been many discussions on this topic. Can anyone > point me to some of the more current and complete discussions on this > topic (on this list or otherwise)? > > The new app will continue to be a desktop app and will have the same > interface (so there is no retraining required to implement the new version). > It currently has the option to have data stored as local .dbf tables > or on an MS SQL table. So we also need to continue to support > local/disconnected data sets. > > We are looking for suggestions on application frameworks, data > libraries (ORM, etc.), VS technologies > (Silverlight/WPF/Winform/ADO/etc.) and other resources that will aid > in the conversion. We are not looking for something that will just > "convert" the code to .net as there are some key architectural changes we want to implement under the hood. > > Any links or other references to point me in the right direction will > be greatly appreciated. Wow! Support doesn't officially end until 2015 I think, and even after that, it should last for YEARS! Look at the large number of FPD, FPW and pre-VFP9 apps out there yet! BUT, I realize you're just a soldier following orders. Are you familiar with any of the DotNet languages? Must it be a Microsoft language? -- Mike Babcock, MCP MB Software Solutions, LLC President, Chief Software Architect http://mbsoftwaresolutions.com http://fabmate.com http://twitter.com/mbabcock16 [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://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.
