Using Installshield Express to install a VFP application 1

[AndrewMozley]

I feel I have been here before !

I am running VFP9 and have created an application, anmprint.exe which runs fine on my machine

I would like to issue this to run on another machine, and want to create an installation file. I understand that this process is not a standard feature of VFP9 - perhaps because the process of installation, gathering files, organising dialogue is not specific to VFP9.

Installshield Express is issued with my copy of VFP9 and I have installed that. I can fire up Installshield Express and create a new project, but then I run out of steam.

Is there a guide available which tells me what files I need to tell IExpress to include in the installation file. Or are there facilities in VFP9 which can guide me through the process.

Also, I see that my fairly old version of Iexpress knows about Windows XP, but not about Windows 7 - where I may also wish to install the product. Will this be a problem?

Thanks, as always

 

[JRB-Bldr]

You will find that many here recommend using InnoSetup (

http://www.jrsoftware.org/isinfo.php)

rather than Installshield Express

Good Luck,
JRB-Bldr

 

[DSummZZZ]

I've used InstallSheild for a few distributions and once you get used to it, well, I haven't had any insurmountable issues. It works well for me.
Just start at the top, read each section thoroughly, understand it, then move to the next item. You will quickly learn what you need and don't.

There are indeed some caveats with W7 that you will need to consider no matter what installer you use (file locations, rights, etc.), but if you refer to FoxWiki, there are some good articles on those.


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[Dan Freeman]

Is there a guide available which tells me what files I need to tell IExpress to include in the installation file. Or are there facilities in VFP9 which can guide me through the process.

To answer this specific question, yes there is. It's in the VFP help file. Look for the topic "Walkthrough: Creating a Visual FoxPro Application Setup Program Using InstallShield"

The same article is online here:

http://msdn.microsoft.com/en-us/library/ms917481.aspx

 

[AndrewMozley]

Thanks jrb. That could certainly be an option. If I can get INNO setup to install an application I would be happy; I have downloaded it and looked at the documentation and a sample .iss file..

I basically need to install a .exe file and several .dbf files. What is the distribution kit that I issue to my customer? Does he have also to install INNO Setup, and do I then issue a folder with my files in it which INNO then copies to a folder which he specifies? I suspect INNO does more than this. Does it perhaps create a .exe file (In the same way as Installshield does), which I can then give to the user to run to install my application?

Does INNO “know” about VFP do the extent of handling the dependencies such as the Visual C runtime library etc. It was this matter (the installation of software on which my .exe file is dependent) which was the subject of my original query.

Thanks again

 

[AndrewMozley]

Thanks Dave and Dan (Installshield). You have given me confidence

And particularly thanks to Dan for answering my specific question. The walkthrough document is helpful in that it mentions about the dependencies such as MSMXL, Visual Foxpro Report applications, Visual C+. That was what I needed to know. (It still seems odd that there is no explicit provision in the VFP development system for telling the Installer what components are needed at run time; I cannot be the first person to have been caught out!)

A few things I am still not clear about.

1. Does it matter what sort of build I use. I tend to distribute software on a USB memory stick. I find that having a build type of either CD-ROM or Single image works equally well. Does it matter which one I use?

2. There is an opportunity to create a shortcut which installs on the desktop. I notice that it finds the program correctly (in the users c:\Program files\Andrew ..\ or whatever folder), but by default it starts the program in the desktop folder. I would like the user to be able to specify (at installation time) where this is to be installed. Is there a facility in Installshield to let him do that?

3. (Perhaps not really an Installshield matter). When I examine the properties of my shortcut, it does not say where it is running the program from., although it clearly does know. Why is this different to the shortcut that I set up to cmd.exe, where it has many more tabs on its properties?

 

[DSummZZZ]

It's in the VFP help file

Silly me for assuming you had already checked the help file.

1. I have used both and they work equally well. As far as I know, the only difference is that the CD install would span more than one CD if needed. The Single Image creates one all encompassing setup.exe.

2. Look at the [INSTALLDIR] settings, which is the default. Then look at "Customize the Setup Appearance". Under that you will see "Dialogs". On the "Destination Folder" dialog, you can allow "Show Change Destination" if you want them to be able to change the install directory.

3. Not sure, but maybe you've left something out in the "Shortcuts/Folders" section? Maybe you need to add the [INSTALLDIR] in the "Working Directory" item.


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[Olaf Doschke]

>It still seems odd that there is no explicit provision in the VFP development system for telling the Installer what components are needed at run time

What do you mean by that? The walkthrough you praise is part of the VFP help, so it's in VFP.

Also in general, Installshield detects dependencies from the EXE or DLL or other files you give it to create a setup of. That's quite comfortable already. And it's working in general, even though it's named Installshield Express for Foxpro the only Foxpro custimization is, that it has the VFP runtime merge modules.

It's just an express version of IS and capable to do any setup, despite having a shrinked feature set. As you already knwo customers will only need the geneerated setup.exe or .msi, the latter requires Windows Installer on the client side, but that's part of Windows anyway.

Inno is needing more knowlegde on your side, but is free software and enables better look and feel and custom actions taken by your setup. the Fox Wiki has some sample Inno Scripts to take over:

http://fox.wikis.com/wc.dll?Wiki~InnoScripts

As you talk of an exe and a couple of dbfs, ISE could be sufficient, it nevertheless has some flaws, eg in Vista/Win7 I've seen horrible statup times. I myself have canceld and kille d a setup in Task manager, which works when waiting a minute (a real minute or two, indeed). ISE is from 2006, so Vista or Win7 were not present and known at that time. Inno is better in that respect.

Bye, Olaf.