![]() ![]() Which is that modified data files will not be overwritten. The way people deal with the situation you describe is to sequence the upgrade (the RemoveExistingProducts call) towards the end of the upgrade (such as after InstallExecute and just before InstallFinalize) which results in the upgrade being installed over the existing product, and file overwrite rules are followed, in particular this one: If it is sequenced "early", such as just after InstallInitialize, then it is effectively still an uninstall of the old product followed by an install of the upgrade, so you lose the config file. Your post implies that you are doing a Windows Installer major upgrade, but you haven't said, most importantly, where the upgrade is sequenced. Is this possible? Or do I need to configure the location in the installer.You should define what "upgrade" actually means. I am looking instead at advanced installer which appears to do everything I need - except the update from install location. Too many times the update just decides to not work on specific machines for no decipherable reason. When an update is accepted, they just replace it.īut I have finally kicked clickonce to the kerb. I dont need to make packages for individual businesses with their specific URL, I just give them the installer and they run it from a share. This works REALLY well for my clients that want to control their updates rather than have them automagically available from my website. I use the clickonce 'feature' that you can configure it so that it looks for updates in the location it was installed from. Users that want access to the latest version - this I can make work with advanced installerĬorporate users that distribute their own updates automatically and simplyįor 2. I also create clickonce packages because of their autoupdate I use a Visual Studio 2017 Installer Project to create an MSI for my project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |