We also had a lot of problems related to the fact that you could not remove the bad add-ons after installing them. Usually we take the following steps:
- Remove the VSTO add-in (using the vstoinstaller / u command)
- Delete directories in the% userprofile% \ AppData \ Local \ Apps \ 2.0 directory
- Delete directories in the% userprofile% \ AppData \ Local \ assembly \ dl3 directory
- Clear ClickOnce application cache (rundll32 dfshim, CleanOnlineAppCache)
If all this still does not work, one workaround if you installed the vsto add-in outside of Visual Studio (if you want to do this) is to temporarily change the assembly name in the properties of the main assembly to something else. He then tricks the Outlook / installer into thinking that this is a completely new add-in that has not been seen before.
Hope this helps.
Casey source share