Extensibility Addin Vs. VSTOAddin

[morna]

Can someone explain the advantage to developing as VSTO Addin vs an
Extensiblity Addin? My target production environment has User's that
do not have admistrator rights to load a VSTO Addin and it is my
understanding that the VSTO Addin can only be loaded and work for the
"Just for Me" option that puts the registry setting in
HKEY_CURRENT_USER.

Is there a way to get the advantage of the shim that is built into
VSTO Addin's for the "Everyone" option (writing keys in
HKEY_LOCAL_MACHINE)?

Thank you for your time.

-Morna

 

[Ken Slovak - [MVP - Outlook]]

It's my understanding from a comment posted by a member of the Outlook team
that Outlook 2007 will ignore any addin registered in HKLM when it starts up
and will not start that addin.

 

[Rafael]

Morna,

You can always use logon scripts to deploy your addin for your users. I
used a VBScript that would check the presence of the addin on the user's
profile and would install it if when not found.


Rafael