Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

RemovePreviousVersions doesn't work?

43 views
Skip to first unread message

Ramil Domingo

unread,
Jan 20, 2004, 5:05:33 AM1/20/04
to
Hi,

Why does the above subject *sometimes* fail? I am aware that you need to
have the same upgradecode but difference productcode in order for the
installer remove the previous version of my application and I am doing it
religiously but still a message pops up saying there is a previous version
of my app installed and I need to remove it from Add/Remove Program utility
just to proceed.

Am I missing something here?

Anybody's help is very much appreciated.

TIA.

Ramil Domingo
Developer


Phil Wilson

unread,
Feb 4, 2004, 7:43:34 PM2/4/04
to
You've incremented the version in the product properties, I assume, but be aware
that VS won't detect versions less than 1.0, so if you expect
RemovePreviousVersions to remove a version like 0.9, it won't work.
The package code needs changing too, but changing the version in the project
properties will prompt you to change that and the product code as well.
There's also a DetectNewerInstalledVersion project property you may have set
True, and that will prohibit version 1.0 replacing version 2.0, so watch out for
that too.
--
Phil Wilson [MVP Windows Installer]
----
"Ramil Domingo" <ram...@togethersoftware.net> wrote in message
news:urfnE0z3...@TK2MSFTNGP10.phx.gbl...

Ramil Domingo

unread,
Feb 8, 2004, 9:47:38 PM2/8/04
to
Hi Phil,

Thanks for the reply. Actually I am installing the same version and yes I
have set the DetectNewerInstalledVersion property to true but it should
proceed with installation since its the same version right? Or I may be
wrong. Will you shed some light here please?

TIA.

Ramil Domingo
Developer

"Phil Wilson" <phil....@unisys.spamcom> wrote in message
news:%230bGXE4...@TK2MSFTNGP11.phx.gbl...

Ot

unread,
Feb 9, 2004, 2:48:01 PM2/9/04
to
I am new to this stuff, too, so take my comments for what they are worth.

There is a version number in the assembly.vb -- presumably the version of
the program/product.

There is also a version number in the deployment project. This is the one
it is detecting and using. If it matches, it seems to me that it assumes
that it is already installed. In order to get an update to install I have
had to increment this version number (and answer "yes" to the prompt), then
when I have "remove previous" set it works as I want it.

Does this match your experience?

"Ramil Domingo" <ram...@togethersoftware.net> wrote in message

news:%23R2Urcr...@TK2MSFTNGP12.phx.gbl...

Ramil Domingo

unread,
Feb 9, 2004, 9:53:03 PM2/9/04
to
Thank so much for the help. I had it working your way. It seems that you
really have to increment the version number of the setup program in order
for it to remove the previous version. I was hoping I could do the same
even if I had the same version.

Anyway thanks again.

Ramil Domingo
Developer

"Ot" <ur...@tds.invalid (use net)> wrote in message
news:O7PZlW07...@TK2MSFTNGP10.phx.gbl...

0 new messages