I created an MSI for one of our applications using WinINSTALL LE, and it works great if the application has never been installed on the PC its being deployed to. If however the application has been installed then the old files do not get overwritten by the MSI. Is there something I can modify in the MSI using ORCA that will force the MSI to replace all the files it installs?

The problem I am having is that the versioning done by the application developers is lame. They went from 17.2.1 to 2.2.2.4 so it things the older version 17 is newer the the actual current version of 2.2 or in the developers mind 2.2=22. Hmmmm.

Thanks.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Until the developers has learned some manner you will need to use the RemoveFile table.
This will make sure the file is removed prior to installing the file from your package.

Information about the RemoveFile table have a look at http://msdn.microsoft.com/en-us/library/aa371201.aspx
Just have in-mind it could fail due to file in-use: http://support.microsoft.com/kb/241928

If the version 2.2.2.4 file is installed with a package you created you could author an upgrade instead.
Upgrade table: http://msdn.microsoft.com/en-us/library/aa372379(VS.85).aspx
Updating Upgrade Table for an Upgrade: http://msdn.microsoft.com/en-us/library/aa372374(VS.85).aspx

Hope that helps
Answered 04/29/2008 by: AngelD
Red Belt

Please log in to comment
0
you can also use a "companion file" to upgrade the item in concern as well.
Answered 04/29/2008 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
Nice call John!

I always seem to forget about the companion file option as I usually do not use it.
Just make sure the companion parent file it depends on does not have the same file version problem.
Companion Files: http://msdn.microsoft.com/en-us/library/aa367997(VS.85).aspx
Answered 04/29/2008 by: AngelD
Red Belt

Please log in to comment
0
i should of linked to it, i was too lazy too look for a link :-)
Answered 04/30/2008 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
I was able to get it to work by creating a record in the property table called REINSTALLMODE with a value of AMUS. I guess it forces the MSI package to run in repair/reinstall mode that will overwrite all the files. I know its not recommended, but it fixed the problem.

Thanks.
Answered 05/01/2008 by: yaplej
Senior Yellow Belt

Please log in to comment
0
John, I wouldn't say you were too lazy but I guess you maybe wanted yaplej to have a try by him self :D
Answered 05/02/2008 by: AngelD
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity