General information
Category:
VFP Compiler for .NET
Environment versions
Network:
Windows 2003 Server
My name is Mike Yeager and I'm the lead developer on the conversion tools from VFPConversion (part of EPS Software).
We'll be updating our web site as soon as we can get to it, but here is some info on the most asked about tools. The cost for the conversion tools is from $1-3K each, depending on the type of license / user.
The Project Analyzer is a FREE tool written in VFP that compiles metrics about your VFP projects. This information is very helpful when trying to determine the scope of a conversion project or even just documenting your investment in VFP. There is also a premium version which costs $129 that gives you much more detailed information by drilling deeper into the source code. It includes information such as the average # of commands per method for a VCX, the number of sub-classing levels for forms, controls and classes, etc. This helps us determine the quality of the code and how well the architecture might convert to .Net.
The Report Converter which converts from FRXs to SSRS has been released for quite some time now and is getting really good feedback. If you're interested, contact us and we'll convert one for you for free. From FRXs to Crystal Reports is not yet ready for prime time.
The Forms Converter has recently been released! It converts all visual classes in both SCXs and VCXs. We don't generally do free samples on this one because most people's forms rely on many, many VCXs and those all have to be converted as well. With this tool, you can configure your target to be plain vanilla .Net controls, Milos Solution Platform controls (EPS's own .Net Framework), Developer Express, Mere Mortals, etc... We have not tested all target frameworks thoroughly, but so far feedback is very good.
We've used both of these tools in projects we've worked on in-house. They're both very fast (measured in forms and reports converted per second!) and they save a LOT of time, especially on large projects with hundreds or thousands of forms and reports.
It's true that we only address the most time-intensive conversion tasks. After having done many conversions and we are constantly looking at all of the conversion techniques out there (including VFP compilers for .Net, calling .Net forms from VFP, calling VFP forms from .Net and many others). We've concluded that a comprehensive automated VFP to .Net conversion just isn't plausible. To be sure Conversion projects, if they are of any size at all, will not be cheap in terms of time or money (if you pay someone else to have it done), however they are much less expensive than a ground-up re-write.
We'd love to talk to you about it if you're facing a conversion project. They're not easy and they're not fun, but they are possible and there are many success stories out there. There are lots of free resources on the VFPConversion web site including a conversion roadmap, white-papers, technical articles about specific tasks, etc.
Mike
Previous
Next
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