RemovePerviousVersion does not appear to work!?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

N4709L - 01 Feb 2004 22:31 GMT

We have used the Setup Wizard within our VB.NET Solution to create a
setup.exe. In the Setup properties we've set the property
RemovePreviousVersions to True. Then, when we select Project, Install from
the menu bar in the VisualStudio development environment it uninstalls the
current installation and then proceeds to install the newer version. That's
exactly what we expect to happen.

However, outside of the development environment, if we run the Setup.exe
that was generated, it complains when there's an earlier version already
installed. It gives us an error message: "Another version of this product is
already installed. Installation of this version cannot continue. To
configure or remove the existing version of this product, use Add/Remove
Programs on the Control Panel."

That's unexpected! Indeed, what we had hoped would happen is that the option
RemovePreviousVersions=True would have cause the Windows Installer to
automatically proceed to remove the current version and install the new one
without bothering the customer to use Add/Remove Programs.

Can you explain how to accomplish the automatic removal of previous
versions, so that one does not need to use Add/Remove Programs to uninstall
the prior older version of the application?

Thanks, -Ron

Reply to this Message

Brian Davis - 03 Feb 2004 00:33 GMT

Ron,

A quick article that covers this can be found at
http://www.knowdotnet.com/articles/autouninstall.html.

NOTE: Be sure to change the Version property of your Setup Project each time
you build. It sounds like that is what is preventing setup from
uninstalling the previous version.

Hope this solves it....

Brian Davis
www.knowdotnet.com

> We have used the Setup Wizard within our VB.NET Solution to create a
> setup.exe. In the Setup properties we've set the property
[quoted text clipped - 20 lines]
>
> Thanks, -Ron

Reply to this Message

N4709L - 03 Feb 2004 11:44 GMT

Thanks, Brian. That works wonderfully. And now I have another excellent Web
site to go to for assistance! knowdotnet.com!

Each time we increment the Version property in the Setup project, should we
answer Yes when it asks if we want to assign a new Product Code and Package
Code? It is the same product, so one would think the answer is No, but the
documentation isn't so clear on this point. It is also a new "package" but
only a new version of the package for this product. Thus, I'd be inclined to
answer No, but the default and recommendation is Yes!

There is an AssemblyVersion in AssemblyInfo.vb. Should we keep the two
Version numbers in sync? In other words, if the Version property of Setup is
8.1.4 Should we use:
<Assembly: AssemblyVersion("8.1.4.*")>

?

Thanks, -Ron

> Ron,
>
[quoted text clipped - 39 lines]
> >
> > Thanks, -Ron

Reply to this Message

Brian Davis - 03 Feb 2004 19:59 GMT

The AssemblyVersion in AssemblyInfo.vb is for a Project, while the Version
property is for the Setup Project. You can keep them synchronized if you
want, but you may want to increment them separately. For instance, if you
did not change your Project at all, but you did change some of the files
that were included with your Setup Project or changed the directory in which
it installs, then you may want to increment the Version of the Setup Project
while leaving the AssemblyVersion of your project alone. Also keep in mind
that there may be several projects in a solution, each with their own
AssemblyVersion. These version numbers may all be different.

From what I understand about the Product and Package Codes, you should
increment them as well to insure that the older version of your app is
removed and replaced with the newer version.

Brian Davis
www.knowdotnet.com

> Thanks, Brian. That works wonderfully. And now I have another excellent Web
> site to go to for assistance! knowdotnet.com!
[quoted text clipped - 14 lines]
>
> Thanks, -Ron

Reply to this Message

N4709L - 04 Feb 2004 05:15 GMT

Thanks. That answers all my questions, and we've implemented what you've
said and it all works great! Thanks a bunch! Case closed!
-Ron

> The AssemblyVersion in AssemblyInfo.vb is for a Project, while the Version
> property is for the Setup Project. You can keep them synchronized if you
[quoted text clipped - 36 lines]
> >
> > Thanks, -Ron

Reply to this Message

RemovePerviousVersion does not appear to work!?

Free Magazines