![]() If this context doesn't make the question clear, let me know. My installation execution sequence is roughly. ![]() The reason why I am scratching my head is that by the time the InstallFiles action executes the destination file no longer resides on the disk. According to the "File Versioning Rules" the new file will not overwrite the old file. The version numbers for various dlls and exes in the old version were messed up. The problem only occurs when I install the new version over top of the old version. If I first uninstall the old version using Add Remove Programs and then install the new version everything works great. If I repair the damaged new installation (Using Add Remove Programs->Modify Installation->Repair), everything is fixed. Even the Program Files\MyProduct directory is removed.īut after uninstalling the old version the installer then only partially installs the new version. So when I execute the new MSI it first uninstalls the old version correctly. I have a new ProductCode for my installation but I have left the UpgradeCode the same. I have newly created setup package (MSI) that installs a new version of my application. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |