1. Create your setup CD / or a set for installtion thru' LAN.
You can prepare your installation set by processing thru the InstallShieldExpress provide along with VFP.
Relevant Microsoft links are provided here.
1. VFP6: Microsoft's Support Question and answer article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;289904&Product=vfp6
2. Though it is for VFP7, it applies to VFP8 as well.(FoxTalk topic)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnfoxtk02/html/ft02a1.asp
3. Again a step by step guide.. again for VFP7 but similar for VFP8.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnfoxgen7/html/vfpdeploy.asp
2. By copying run-time files directly in application directory or to respective Common Directories.
1. VFP7 : A minimal set of DLL's for VFP7 application required can be seen in this link.
http://fox.wikis.com/wc.dll?Wiki~VFP7RuntimeFiles
2. VFP8 : A minimal set of DLL's for VFP8 application required can be seen in this link.
http://fox.wikis.com/wc.dll?Wiki~VFP8RuntimeFiles
While I have said this, I do not recommend this method of copying the run-time files. This could work in some cases, but not always. My suggested way is below.
**********************************************************
3. My suggestion
1. Create a setup disk as explained above without any application,
(a) Whenever a version upgrade is done.
(b) Whenever a new Service Pack is applied
(c) Whenever you change the ActoveX or such components which need setup and registration in users computer.
Copy this in your sharable network place and then proceed to install it in clients computer whenever changes are taking place. This will be handy and when you change your application executable, it will be enough, if you copy that application in server. There will be no need to do the complete set everytime in all users computer.
2. A step further, create the set up set whenever 1(a) and 1(b) happens. The instances will become far fewer and the setting up will become easier. Whenever you change the ACtiveX or such components, install it using your own VFP code or by batch files.
This is only a short list and detailed list can be seen in above specified links..
VFP6 - Run Time Files
*********************
VFP6R.DLL
VFP6RENU.DLL
VFP7 - Run Time Files
*********************
MSVCR70.DLL (to be kept in Windows system32 directory)
VFP7R.DLL (can be in application directory)
VFP7T.DLL ( .. )
VFP7RENU.DLL ( .. )
But the last three files are to be kept in ...
\Program Files\Common Files\Microsoft Shared\VFP\ directory while the application directory is also enough.
VFP8 - Run Time Files
*********************
MSVCR70.DLL (to be kept in Windows system32 directory)
gdiplus.dll (to be kept in \Program Files\Common Files\Microsoft Shared\VFP\)
VFP8R.DLL (can be in application directory)
VFP8T.DLL ( .. )
VFP8RENU.DLL ( .. )
But the last three files are to be kept in ...
\Program Files\Common Files\Microsoft Shared\VFP\ directory while the application directory is also enough.
In the above, instead of ENU you may need to include appropriate language pack.
This list does not include the ActiveX or such components (you migt have used in your application). You may need to distribute these as well in addition to your application executable.
**********************************************************
Ramani
(Subramanian.G, Winner Software / FoxAcc Software.)
www.winnersoft.coolfreepages.com
**********************************************************
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.