Setup Package Does Not Replace Obsolete Files

  • Thread starter Thread starter TC
  • Start date Start date
T

TC

I have a deployment project which is supposed to install an application
to the Program Files folder. I have set RemovePreviousVersions = True.
Nevertheless, I find that the obsolete version of one critical file is
not removed and is not replaced by the current version.

What is going on? Why isn't the file uninstalled by the setup program,
and why isn't it overwritten? I've been scouring the .NET help pages,
but I can find nothing to explain this behavior.


-TC
 
I've researched the problem and I can answer my own question.
Basically, RemovePreviousVersions doesn't work. Microsoft doesn't
acknowledge this in their knowledge base, but there are plenty of
newsgroup posts confirming the bug. There is apparently a workaround,
but it is highly technical.

-TC
 
I have seen numerous posts confirming what you are saying, but I have also
found some that say RemovePreviousVersions = true works but only if you
change the version #. When you change the version # and recompile then run
the installer it removes the old version and installs the new 1. I use
this and it appears to work for me.

Hope this helps.

~SPO
 
Back
Top