yep. we have no control over this. vs isn't very good at managing addins. i hope to move to a vs extension based system which will not suffer these problems.
and to give an idea of how bad vs is with this:-
1) some users had multiple tool bar controls. This problem was vs telling the addin that it needs to re-run its internal setup but vs has not cleared the vm controls
2) some users have missing tool bar and menus after upgrade of vs. This problem is vs clearing our controls but not telling the addin to re-run its internal setup
It's very fustrating and worse for me because every time I want to change my addin from dev location to release/test I get the problem! We have NO control over this.
It is complicated by that fact that vs allows two types of control creation. Temporary and permanent.
Temporary are best because they get re-created each time vs loads (such as boards and libraries etc).
However if we want to add tool bar objects that you can alter the width of (such as boards drop down list) or if we want to add menu items to vs menus that are sometimes hdden we have to use permanent controls.
If we put a temporary control on a vs menu item that vs sometimes hides (such as project specific) then vs fails to hide the menu.
It's the permanent controls that are always the problem but we would not be so neatly integrated without them
Roll on extensions which are more complicated and difficult to implement but don't appear to suffer the addin problems.
I need a drink!