By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,148 Members | 759 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,148 IT Pros & Developers. It's quick & easy.

Installer question: Spurious entries in Add/Remove Programs

P: n/a
Greetings,

I am working on a program that is in beta testing and goes through a new
version every week or so.

When there's a new version, go into the setup project change the Product
Code but leave the Upgrade Code and version number unchanged.

RemovePreviousVersions is set to True.

When the user installs the program, it overwrites the previous (nominally
same) version just fine.

But there are then two entries in Add/Remove Programs. "Removing" either
one of them will remove the program. If I then "remove" the other one, it
does something that doesn't raise any errors, but doesn't seem to have any
effect either.

Have I found a bug in Visual Studio 2003 or the Microsoft Installer? What's
up?

Thanks!
--
Michael Covington
Consultant
www.covingtoninnovations.com
Nov 15 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
I've gotten a partial answer which leads to a bigger question.

Microsoft, at
http://support.microsoft.com/default...b;en-us;300540
says that in this situation I should be changing only PackageCode, not
ProductCode.

OK... where on earth is PackageCode?

I can't find it in Setup Project Properties or even the help system.
Nov 15 '05 #2

P: n/a
Still more news.

Apparently the Package Code changes every time an .msi file is gnerated. So
far so good.

The problem is in setup.exe.

After rebuilding my deployment project, if I want to reinstall using
myapp.msi, over what the Installer thinks is the same version of the program
already there, I can choose "Repair" and everything goes just fine.

But SETUP.EXE refuses to run in that situation. It tells me the current
version is already installed and I must go to Add/Remove Programs and
"Change" it. If I try to do that, I get told that the .msi file is not
valid.

What is the PROPER way to distribute MINOR upgrades of a product, with
either the same or a slightly different version number?

Thanks to anyone who can shed light on it!


"Michael A. Covington" <lo**@www.covingtoninnovations.com.for.address> wrote
in message news:%2******************@TK2MSFTNGP10.phx.gbl...
I've gotten a partial answer which leads to a bigger question.

Microsoft, at
http://support.microsoft.com/default...b;en-us;300540
says that in this situation I should be changing only PackageCode, not
ProductCode.

OK... where on earth is PackageCode?

I can't find it in Setup Project Properties or even the help system.

Nov 15 '05 #3

P: n/a
More news: I was wrong. Behavior of myapp.msi is just the same as
setup.exe

If I rebuild my deployment application, I can't install it until I remove
the previous "version".

"Michael A. Covington" <lo**@www.covingtoninnovations.com.for.address> wrote
in message news:%2****************@TK2MSFTNGP11.phx.gbl...
Still more news.

Apparently the Package Code changes every time an .msi file is gnerated. So far so good.

The problem is in setup.exe.

After rebuilding my deployment project, if I want to reinstall using
myapp.msi, over what the Installer thinks is the same version of the program already there, I can choose "Repair" and everything goes just fine.

But SETUP.EXE refuses to run in that situation. It tells me the current
version is already installed and I must go to Add/Remove Programs and
"Change" it. If I try to do that, I get told that the .msi file is not
valid.

What is the PROPER way to distribute MINOR upgrades of a product, with
either the same or a slightly different version number?

Thanks to anyone who can shed light on it!


"Michael A. Covington" <lo**@www.covingtoninnovations.com.for.address> wrote in message news:%2******************@TK2MSFTNGP10.phx.gbl...
I've gotten a partial answer which leads to a bigger question.

Microsoft, at
http://support.microsoft.com/default...b;en-us;300540
says that in this situation I should be changing only PackageCode, not
ProductCode.

OK... where on earth is PackageCode?

I can't find it in Setup Project Properties or even the help system.


Nov 15 '05 #4

P: n/a
So, I'm a little lost on this thread, but one thing I noticed... you MUST
change the version of your setup project, otherwise RemovePreviousVersions
doesn't understand that there's an older version, just the same version.
But since the PackageCode has changed, it installs it, instead of going to
the repair/remove dialog.

---
David Guyer - VBQA Deployment Testing
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
From: "Michael A. Covington" <lo**@www.covingtoninnovations.com.for.address>References: <um**************@TK2MSFTNGP12.phx.gbl> <##**************@TK2MSFTNGP10.phx.gbl>
<#B**************@TK2MSFTNGP11.phx.gbl>Subject: Re: Installer question: Spurious entries in Add/Remove Programs
Date: Sat, 8 Nov 2003 17:22:38 -0500
Lines: 53
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <eu**************@TK2MSFTNGP10.phx.gbl>
Newsgroups: microsoft.public.dotnet.languages.csharp
NNTP-Posting-Host: 66-23-192-94.clients.speedfactory.net 66.23.192.94
Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP10.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.languages.csharp:197647
X-Tomcat-NG: microsoft.public.dotnet.languages.csharp

More news: I was wrong. Behavior of myapp.msi is just the same as
setup.exe

If I rebuild my deployment application, I can't install it until I remove
the previous "version".

"Michael A. Covington" <lo**@www.covingtoninnovations.com.for.address> wrotein message news:%2****************@TK2MSFTNGP11.phx.gbl...
Still more news.

Apparently the Package Code changes every time an .msi file is gnerated.

So
far so good.

The problem is in setup.exe.

After rebuilding my deployment project, if I want to reinstall using
myapp.msi, over what the Installer thinks is the same version of the

program
already there, I can choose "Repair" and everything goes just fine.

But SETUP.EXE refuses to run in that situation. It tells me the current
version is already installed and I must go to Add/Remove Programs and
"Change" it. If I try to do that, I get told that the .msi file is not
valid.

What is the PROPER way to distribute MINOR upgrades of a product, with
either the same or a slightly different version number?

Thanks to anyone who can shed light on it!


"Michael A. Covington" <lo**@www.covingtoninnovations.com.for.address>

wrote
in message news:%2******************@TK2MSFTNGP10.phx.gbl...
> I've gotten a partial answer which leads to a bigger question.
>
> Microsoft, at
> http://support.microsoft.com/default...b;en-us;300540
> says that in this situation I should be changing only PackageCode, not
> ProductCode.
>
> OK... where on earth is PackageCode?
>
> I can't find it in Setup Project Properties or even the help system.
>
>




Nov 15 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.