luxebas.blogg.se

1. #Cannot uninstall teamviewer 12 msi wrapper how to#
2. #Cannot uninstall teamviewer 12 msi wrapper install#
3. #Cannot uninstall teamviewer 12 msi wrapper update#
4. #Cannot uninstall teamviewer 12 msi wrapper upgrade#
5. #Cannot uninstall teamviewer 12 msi wrapper registration#

#Cannot uninstall teamviewer 12 msi wrapper update#

The reasons why we have the problems this bug is about are complicated, but they boil down to the surprising level of difficulty in migrating existing installations and being compatible with our existing update system (which the majority of our users do need). The feedback that I've seen has contained a surprising (to me) amount of complaints about this particular bug, so even though I was initially dismissive, I now think that was the wrong attitude and I'd like to get this addressed somehow. Currently that file is generating the thin wrapper that's discussed in bug 1475510, and that route was chosen because it allowed us to get something shipped quickly that would help in at least some situations and that we could start collecting feedback on. It can be a bit tricky to use, but it's doing the job. The tool we're using to generate our MSI is WiX, which I'm sure is one of the tools you've found in your searches. I'll try to provide some more context about the current situation. Thanks for offering to help! If you think you can do something to improve this situation, please feel free to start working on it. Who i can contact to offer my help to work in this issue? Also widely used and long existing opensource tool. I checked some internet sites and found a dozen of tools to build an msi package. Now its just a small step ahead for a true and real integration for Firefox in Business enviroments. It's great Firefox does finally support gpo's. So there is no way around SCCM deployments. Some business critical procedures will be affected and we need a careful rollout and deep testing before. In the future Microsoft will even push more the use of SCCM because of the product cycle philosophy of Win10.īy the way, allow autoupdate a software is never an option. We and a lot others companies using SCCM as solution to keep our environment up to date. I work as admin in a small company with about 50 Workstations. Each little Tool has a working installer, so its not a big deal. It's not understandable why Firefox is the only important software out there in the world without a working MSI package. 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.

#Cannot uninstall teamviewer 12 msi wrapper install#

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.

#Cannot uninstall teamviewer 12 msi wrapper upgrade#

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.

#Cannot uninstall teamviewer 12 msi wrapper registration#

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.

#Cannot uninstall teamviewer 12 msi wrapper how to#

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.