Wiki Home

VFP 8 Runtime Files


Namespace: WIN_COM_API
  • See also Mike Stewart's Walkthrough: Creating a Visual FoxPro Application Setup Program Using InstallShield Express in VFP8 help or in the MSDN online
  • See also http://www.alvechurchdata.co.uk/foxfiles.htm
  • * For some Ready-to-go Runtime Installers see wOOdy's archive at Code.Msdn.Microsoft.com/FoxPro
  • For some Ready-to-go Runtime Installers see wOOdy's contribution at VFPX.org
    A minimal set of DLL's for VFP8 application
    DLL Name Register
    (order)
    Default Location Other Locations Comment
    msvcr70.dll No (1) WinSysDir WinSysDir, App Folder VC++ 7.0 Runtime library
    gdiplus.dll No (1) Common Files\Microsoft Shared\VFP --"-- GDI+ support
    vfp8r.dll Yes (3) --"-- App Folder, WinSysDir STDLL and EXE support
    vfp8t.dll Yes (3) --"-- --"-- MTDLL support
    The runtimes for the language(s) you support:
    vfp8renu.dll No The same as vfp8r.dll The same as vfp8r.dll English
    vfp8resn.dll --"-- --"-- --"-- Spanish
    vfp8rdeu.dll --"-- --"-- --"-- German
    vfp8rfra.dll --"-- --"-- --"-- French
    vfp8rrus.dll --"-- --"-- --"-- Russian
    vfp8rcsy.dll --"-- --"-- --"-- Czech
    vfp8rkor.dll --"-- --"-- --"-- Korean
    vfp8rchs.dll --"-- --"-- --"-- Chinese (PRC)
    vfp8rcht.dll --"-- --"-- --"-- Chinese (Taiwan)
    To provide compressed HTML help (CHM) within your apps:
    foxhhelp8.exe Yes
    Microsoft Shared\VFP WinSysDir foxhhelp8.exe /regserver
    foxhhelpps8.dll No --"-- --"--
    XMLTOCURSOR() function requires MSXML 3 :
    msxml3.dll Yes WinSysDir WinSysDir
    msxml3r.dll No --"-- --"-- Required by msxml3.dll
    msxml3a.dll --"-- --"-- --"-- --"--
    XMLAdapter class requires MSXML 4 :
    msxml4.dll Yes WinSysDir WinSysDir
    msxml4r.dll No --"-- --"-- Required by msxml4.dll

    Note: for VFP7 and above, you should not be putting DLLs in WinSysDir. I don't remember if it was a Win 2 K or WinXP change, but Microsoft is strongly discouraging that, for Dll Hell reasons (I think). They should go in Program Files\Common Files\Microsoft Shared\VFP, as is given in the Default Location above.
    You DON'T have to register the DLLs as long as you put them in the same directory where your application is installed. That's the way we distribute our products and we have no problems doing that.

    Install Order is important!
    It appears the order of how things are installed is also important. GDI+ should be installed before the VFP runtimes becacuse without it installed the VFP runtime won't register.

    I installed the runtime on a Windows NT Server, on which I also needed to keep VFP 7 runtimes going. I also had VFP web apps running while doing this. It's easy to copy the VFP files as indicated above and register the two that require it. For msvcr70.dll, a newer version seemed to apply, but I could not just copy it into WinSysDir (access violation). I found that shutting down the web apps for a few seconds let me copy the new one in. Then I could register VFP 8 runtimes, and all apps, both VFP 7 and 8, ran fine on the NT Server. -- Randy Pearson

    MSXML 3 for XMLTOCURSOR() function
    You also need MSXML 3 if you plan on using XMLTOCURSOR() function in VFP. Manually installing MSXML on Win 2k/XP/Server is a problem because you can't overwrite MSXML in the SYSTEM directory without a reboot and copying the file to a special occasion. Hopefully whatever install mechanism you use can deal with this. For manual installs I suggest copying and registering the file only if it doesn't exist already.

    MSXML 4 for XMLAdaper
    If you're using XMLAdapter you'll have to install MSXML 4 also.

    See Also InstallShield Express And Vfp 8, VFP Runtime Compression,
    See also VFP Runtime Files: VFP 7 Runtime Files - VFP 8 Runtime Files - VFP 9 Runtime Files - Unlimited Free Runtime
    Contributors Alex Feldstein, Sergey Berezniker, Rick Strahl, Randy Pearson, ?wOOdy
    Category VFP Installations Category VFP Tips And Tricks

  • ( Topic last updated: 2015.04.15 12:28:50 PM )