![]() I don't recommend using the application registry keys (the ones in SOFTWARE\Mozilla) because I can't guarantee the structure of those keys won't change. As a second alternate, the uninstall registry key that we do create contains the install path and also the version number. If file version info isn't easy to check, the application.ini file also contains the version number, so that would be a good first alternate. Yes, the most reliable indicator is the version info on the firefox.exe file at your installation path it will always be correct and up to date and reflect the version of the product that is actually installed. I know i could just start picking pieces of metadata at random but I would prefer to have something from the team as the next best option. Just checking by executable name does not really do much if there is a build over build upgrade happening because it would already exist, you would also need to check for file details, I am wondering what the FF dev team is recomendingas the best solution since as of now MSI guid is not an option. (In reply to wildtyphoon87 from comment #11) And there's probably something else that needs to be done that I'm not thinking of right now. This might be impossible, but it might also not be a problem, I'm not sure. Figure out some way to update the MSI uninstall registration with the correct display version when the installation is updated.This change also needs to affect updates, which means we need to add something (I'm thinking a registry value) that PostUpdate can use to know whether it is updating an MSI installation or not. Have the regular installer skip writing its normal uninstall registration when run from an MSI.I'm also just making an assumption that custom uninstall actions are even a thing, I haven't looked into how to do that. This is the part that I'm least sure about it's not immediately clear to me how to implement that action. Add a custom uninstall action that finds and runs the helper.exe uninstaller.Remove the hack that prevents the MSI from registering an installed product.I think the quickest route to a solution for this (that doesn't involve rearchitecting all of both install and update from scratch and building a conventional MSI) would be something like this:
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |