ext_cm_UISetup is fired only once in the life of the add-in and is used to
create UI commands (and permanent toolbars if you choose not to use
temporary toolbars) that must be created only once. So, normally you only
receive ext_cm_Startup, etc. but not again ext_cm_UISetup
There is a registry entry that it is modified when ext_cm_UISetup has been
fired, to not fire it again. It is documented in the MSDN help.
--
Carlos J. Quintero
MZ-Tools 4.0: Productivity add-ins for Visual Studio .NET
You can code, design and document much faster.
http://www.mztools.com "chofra03" <chofra03@discussions.microsoft.com> escribió en el mensaje
news:10909DFB-91C1-4008-AA72-AEADE1C00B5D@microsoft.com...
[quoted text, click to view] > Hi,
>
> Recently I build a Addin application from scratch based on Addin
> application
> source that I got on the internet.
>
> While building, installing and starting the based Add-in in debug mode,
> once
> the OnConnection method is called, while looking at the
> Extensibility.ext_ConnectMode connectMode parameter, I got the
> ext_cm_UISetup
> value each time the addin is launch for the first time.
>
> With my Add-in application, I performs the same step as the based
> application but I could not get the ext_cm_UISetup value for the
> Extensibility.ext_ConnectMode connectMode parameter. I always got the
> ext_cm_Startup.
>
> Does anybody knows the solution to this problem or any related tip.
>
> Thanks,
> --
> Francois Chouinard