Installshield for VFP 7.0 3

[fmoore0001]

Okay, I got a new problem with Installshield that is baffling me. I made an install for it, worked fine. Then I upgraded the program code recreated the install, but when I use it it insists I already have the program installed.

In Visual Studio 6.0 I just incremented the Installer. What do I need to do here?

Frank

 

[Mike Lewis]

Hi Frank,

If the only change you made was to the EXE, then you don't need to build another InstallShield project. Just give the new EXE to the user, and have them copy it over the old one.

The only other option (as far as I know) is for the user to uninstall the application (from Control Panel) and then install the new one. But that would be a lot of effort.
Mike Lewis
Edinburgh, Scotland

http://www.ml-consult.demon.co.uk

 

[fmoore0001]

I can't believe that is the only way! Even Visual Studio Installer 6.0 has the ability to replace. If that is the case ten Installshield is worthless as a commercial installation tool.

My users are, for the most part, many and computer idiots. An Installer is the only way I would trust them to do ANYTHING without messing it up.

Frank

 

[itflash]

I know what you mean...

the way I did it was to give them a shortcut to a self extracting exe

and placed the shortcut on the desktop during installshield installation.


ITflash

 

[Mike Gagnon]

fmoore0001

The only way you could have done it with Installshield was on the first install, select the uninstallable option (which you may not have selected) and when the upgrade comes, it would prompt you to update (Uninstall the current version to install the new one.) Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[fmoore0001]

Mike, ??? Where is this? It is a setup option?

I am beginning to think that Visual Studio 6 is still the better option. I have people instaling and updating all the time.

Frank

 

[Mike Gagnon]

fmoore0001

Directly from the InstallShiedl Help File:
Create an Uninstallation Shortcut

It may be useful to provide your customers with an easy way to uninstall your product. Of course, they can always navigate to the Add/Remove Programs applet and select your application from the list, but how many people know how to do that or even want to go through the trouble? Follow the steps below to create a shortcut that, when launched, automatically starts your application's uninstallation process.


Navigate to the Shortcuts/Folders view by clicking the Shortcuts/Folders icon on the checklist.
Right-click on Program Files folder and select New Shortcut.
Rename this shortcut by selecting it, pressing F2, and typing in the new name.
In the Feature property, select the feature you would like this shortcut to be associated with. Preferably, this shortcut would always be installed and should, therefor, be associated with the feature Always Install.
In the Arguments field, enter /x followed by the product code as it appears in the General Information view (the braces are required)—/x {662C3E37-5411-11D4-BB85-00C04F49BC03}, for example. Separate the two arguments with a space.
In the Target field, select [SystemFolder] from the list. Append /msiexec.exe to this location.

Msiexec.exe is the command-line engine for the Windows Installer service. The /x argument instructs the Windows Installer service to uninstall the product referenced by the product code you entered in the Arguments field. You can finish your shortcut by selecting an icon for it and by giving it a description.

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[ramani]

HI
IN your InstallShieldExpress,
(1) ORGANIZE your setup
..
..
UPGRADEPATHS
This is the area using which you can do the upgrades. Unfortunately that is locked, because we are provided with a limited edition. Microsoft wants to provide you with something and then telling you to buy full version for better ones.

May be look for an alternative freeware..
Give a try.. on this one..

http://www.jrsoftware.org/

I have not tried, but intent trying. When they talk about VB, why not VFP as well.

Another important point.. May be you provide the first setup using VFP way and then upgrades etc using the freeware setup suggested.
ramani
(Subramanian.G),FoxAcc, ramani_g@yahoo.com

 

[fmoore0001]

Mike, thanks for the info. But, I am now very disappointed in Installshield. Visual Studio Installer 6.0 does everything for the install AND knows the difference from a new install to an upgrade. I cannot (or maybe I can) believe that Microsoft would allow such a poor implementation of installshield to ship with VFP. It is more like shareware then a professional install system.


Frank

 

[Mike Gagnon]

Frank

It is more like shareware then a professional install system.

I find the fact that you cannot just install an application over an existing one a feature, not a defect. And BTW If you ever tried the other install programs out there, you are in for a surprise, the learnign curve is a lot steeper then InstallShield fro VFP.

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[fmoore0001]

Don't I know that! It tooks me months to fully understand the Windows Installer in Visual Studio 6. But, my point is when I paid all the money for this version that it should have had a fully implemented installer. Just my opinion. When I got the full ($1400) enterprise addition of Studio 6 (which included Foxpro) I had an installer. I am not going to change Microsoft's mind, but it is different than what I got before. Tired of getting nickel and dimed by Microsoft. Again, my opinion.

Frank

 

[wgcs]

> But, I am now very disappointed in Installshield.

> Tired of getting nickel and dimed by Microsoft. Again, my opinion.


Not just your opinion, My opinion too! Though, of course, it's not just MS.. InstallShield is the one who gets paid this time!

After having a number of customers complain of the "unprofessional" aspect of having to first Uninstall the old version of our software before installing the new version, we caved in and paid the $150 for the upgrade to the Full IS Express.

ISE, however, still has a different mind set than I like, but it works. Basically, to build an upgrade, you have two options: Either jump through a bunch of hoops, archiving every release, and build a 'differential' upgrade (patch), or just change the ProductID on every build, and then you can simply have the upgrade install everything over top the original installation.

We (can you guess), opted for the second, and my only annoyance is that ISE doesn't have a setting to automatically change the ProductID with every install build.

(If you don't change the productID, then when the user tries to install, it complains that "this product is already installed... please uninstall before continuing". All that changing the productID does for you is automates the un-install before installing the "new product", and then, only if the Upgrade Path matches).

 

[fmoore0001]

Thanks for the info. And, I agree 100%. For me I may as well stick with Visual Studio 6 for now.

Frank

 

[Sholahudin]

I agree with the peoples, ISE it's make me crazy