Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Setup Problem

Status
Not open for further replies.
Jan 14, 2003
7
0
0
US
IN a setup project
I tell the installer to uninstall any previous version, and to detect if a newer version exists. I set a new version number and it generates product code updates. If I attempt to right click on the setup project name and choose install it performs correctly in that it removes any previous version and installs the new version.

IN my code I detect if a newer version exists on the server or not.
If it does, I download:

Instmsia
my msi file
InstMsiW.Exe
setup.exe
setup.ini

IN my code after it does this I make this statement:
System.Diagnostics.Process.Start("C:\JJ Koepsell Customer Software 1.0 Setup Program.msi")

I also tried calling the setup.exe file instead of the msi file with the same result.

and then

I shut down the program.

The program installs (no dialog indicating the current program is being uninstalled) but in the add/remove programs menu the previous version is still listed there along with the new version There are 2 listings for this program now). In the actual program folder however there does not appear to be 2 installations.

How do I get rid of the old version and install the new?

How do I deal with this..........I am under a huge deadline.....

 
Update I have been informed that:

"You may have run into a VS.NET issue with RemovePreviousVersions (fixed in
VS 2003). You install a per-system (Everyone) product, then build a new
version and change product and package codes and update the product version,
setting RemovePreviousVersions. The problem is that the install defaults to
per user (just me), but a per-user install won't upgrade a per-system
install so you get two products on the system. A detour is to edit the MSI
file with Orca and move the FindRelatedProducts action (in the
InstallUISequence) to be just before ExecuteAction, so that old product
detection occurs after the per-user/per system decision has been made."

Please tell me how to do in a step by step method:

"A detour is to edit the MSI
file with Orca and move the FindRelatedProducts action (in the
InstallUISequence) to be just before ExecuteAction, so that old product
detection occurs after the per-user/per system decision has been made."
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top