VPF > Install Shield> Build

Untick the three options.

Chriss

As I mentioned near the start of your thread184-1820175, Inno Setup is usually the best choice for creating install programs. It takes a bit of work at first to create your initial script, but once you have done that, it's easy to adapt if for other projects. I have used it for at least half a dozen projects, and I've only had to change a few lines in the script each time.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads

Well, I also said it's not the only thing available.

myself said:

you can use anything else free or commercial on the market to create setups

Click to expand...

And I said

myself said:

The only thing you profit from using installshields in this outdated version is, that it can work with the merge modules that are installed with VFP that cover C++ runtime, VFP runtimes, xml3, xml4 and the different language resource DLLs like VFP9rcsy.msm for Czech and many more.

Click to expand...

Of which "The only thing you profit" and "outdated" implicitly point out that you only have a slight advantage with merge modules, and that it's old an there are better things.

You still could have made the Installshield project to work, if you untick these options. Simply read what it wrote it has problems with. An icon it tries to extract from the exe. You could either not at all create shortcuts and thus not need icons or use any icon. I have no idea why the dialog you posted a screenshot of defaults to an ico file that's not existing on the desktop at all. That must have specified sometime earlier. But if that's the case of course that also isn't replacing its default try to extract an ico from the EXE. The simplest for Installshield seems to use a dedicated simple ico file instead.

Just read everything in your screeenshot. In itself it already points out what else you can do. You really just have to read this.

Chriss

Yes, you're right, I just joined the thread because you wrote it there, I've tried several programs and this one is really the best and easiest to create an installation and write a .dll file.

I couldn't insert the ico file, later I found out that after inserting the program it crashed and said that I don't have a full license, so it was only possible to create a setup without the main icon of the program. I thought it was some kind of mistake, but it was just a full license of the program, while I installed this program from a CD that was purchased historically.

However, I don't deal with it anymore, I uninstalled everything and work with what is functional and simpler.

That's not at all what I meant.

"Use alternate shortcut icon" is ticked. All your trouble goes away, if you UNtick that. Isn't that clear? From the text itself?
Do you want to use an alternate shortcut icon? No, not at all. You don't need one.

And if you don't know how: In the VFP project you can specify an icon that's put into your gpt_sisk_sestav.exe and then automatically used in shortcuts to it as default. That is, if you even want to create a shortcut. Since Vista the program menu is pretty much obsolete and you do things different anyway, the only shortcut you could offer is on the dektop. What's in the taskbar is technically also a shortcut, but that's not just a lnk file to put somewhere anyway. And that, by the way, is not at all VFP specific, it's just Windows.

It sounds like you didn't install Installshield Express from the VFP CD, but a full version. Well, and if you did use Installshield from the VFP CD and it told you some features are not licensed, yes, it's an Express version, thus the E in ISE. It's not a full version. But creating a setup.exe is among the features supported. If that didn't work out in the end for you, I don't know what you did. It works overall, though.

Anyway it is, you now switched to something completely different, I have noticed that, no worries. You surely have a better set of features available, handling merge modules isn't a necessity. I don't know what you mean with writing a dll file, Any installation creation tool I know doesn't create an installation DLL, they create the usual setup.exe or an msi. A setup may analyze a dll to register COM classes from it. But that's not a necessity, too. The VFP runtime DLLs that can optionally be registered will be registered by using the VFP runtime merge module.

Chriss