By Imran Salahuddin | January 27th, 2015 |
In a perfect world, we wouldn’t need a FoxPro conversion. The architects of all your vital applications would have the time and assets to fully convert applications into self-contained arrangements, but we don’t live in that world.
When it comes to a FoxPro conversion some have often recommended applications, usually from small and autonomous developers, that necessitate some version of the .NET Framework be installed to function but…
In most cases when making a FoxPro conversion, applications will ask for a specific version of the framework to be installed.
We’d recommend against installing that particular version and trying as an alternative, installing the most up-to-date FoxPro conversion, assuming your Windows OS supports it.
Most .NET packages contain backwards compatibility, so an application asking for the 2.0 framework can generally get by with what’s packed into the latest version. Be sure that you’re current on your Windows Updates, as there may be important system patches that need installing before a FoxPro conversion will fit securely on your system.
One foreseeable problem with making a FoxPro conversion is a need for space, even if your system doesn’t make that clear. For example, the 4.0 version of .NET for standard 32-bit Windows systems requires 850 MB of free space on your primary Windows drive; a 64-bit Windows system needs 2 GB free, and Windows typically won’t ask you if you have space on another panel to spare.
If your free space is smaller than these amounts, you’ll need to look at your hard drive and free up some space.
Cheers to hoping you and .NET can co-exist soon! To learn more about how the process works go to our video blog.