Re: Using Visual Studio Installer, create an Outlook COM component that can only be installed by an administrator but, once installed, runs for all users
From: Tom Winter (tom_at_nospam.amosfivesix.com)
Date: 02/12/05
- Next message: Ralph: "Re: VB newbie - exposing VB subs to VBA?"
- Previous message: Lance Wynn: "Re: Custom Collection - NewEnum - Type Mismatch"
- In reply to: Ken Slovak - [MVP - Outlook]: "Re: Using Visual Studio Installer, create an Outlook COM component that can only be installed by an administrator but, once installed, runs for all users"
- Next in thread: Helmut Obertanner: "Re: Using Visual Studio Installer, create an Outlook COM component that can only be installed by an administrator but, once installed, runs for all users"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 12 Feb 2005 12:07:10 -0500
I can provide you with a REG file that "extends" the VB6 Add-In Designer so
it allows options for registering your add-in under HKLM. What the heck, I
just include it right now: This adds entries for Word and Outlook to be
registered under HKLM. You should be able to do the same for other Office
apps. After adding these reg entries, the next time you start VB6, other
entries will show up in the drop down menus in the Add-In Designer.
--- Tom Winter tom@nospam.amosfivesix.com ---------------- REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\AddIn Designer] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\AddIn Designer\Microsoft Outlook (All Users On Local Machine)] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\AddIn Designer\Microsoft Outlook (All Users On Local Machine)\Microsoft Outlook 9.0] @="HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Office\\Outlook" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\AddIn Designer\Microsoft Outlook (All Users On Local Machine)\Microsoft Outlook 9.0\LoadBehaviors] "Load at next startup only"=dword:00000010 "Load on demand"=dword:00000009 "Startup"=dword:00000003 "None"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\AddIn Designer\Microsoft Word (All Users On Local Machine)] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\AddIn Designer\Microsoft Word (All Users On Local Machine)\Microsoft Word 9.0] @="HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Office\\Word" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\AddIn Designer\Microsoft Word (All Users On Local Machine)\Microsoft Word 9.0\LoadBehaviors] "Load at next startup only"=dword:00000010 "Startup"=dword:00000003 "Load on demand"=dword:00000009 "None"=dword:00000000 -------------- "Ken Slovak - [MVP - Outlook]" <kenslovak@mvps.org> wrote in message news:OeX$t33DFHA.624@TK2MSFTNGP15.phx.gbl... > Please do not post to so many groups, pick one or two. > > Addins registered in the HKCU hive of the registry are "user" > installations and will only be available to that user. They also show up > in the COM Add-Ins dialog. > > Addins registered in HKLM are "administrative" installations and are > available to all users. They don't show up in the COM Add-Ins dialog. > > If you use a Designer and allow the COM addin DLL to self-register or > allow the installer to extract COM registration information then your > addin will end up registered in HKCU, even if you explicitly create the > necessary registry entries in HKLM in your installer. That can cause > problems. > > What I do when I want to create an administrative installation is to use a > class module instead of using a Designer. That way there is no > self-registration information in the DLL that points it to HKCU. I add the > Implements IDTExtensibility2 statement that usually would be in the > Designer to the class module. Then I enter the registry information for > registering the addin myself to the HKLM hive in my installation package > (that's the method you have to use for VB 5 addins of both types, VB 5 > doesn't have Designers). > > -- > Ken Slovak > [MVP - Outlook] > http://www.slovaktech.com > Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003 > Reminder Manager, Extended Reminders, Attachment Options > http://www.slovaktech.com/products.htm > > > "TC" <getmyemails2@yahoo.com> wrote in message > news:eMY6sQvDFHA.1260@TK2MSFTNGP12.phx.gbl... >> Hello, >> >> I am building a COM component that is to be used with MS Outlook on >> Windows 2000 and later using Office 2000 and later. >> >> I want the installation to only work when an administrator runs the >> installer and, once successfully run by the administrator, makes the >> component available to all users of that machine. >> >> Can anybody point me in the right direction? >> >> Thanks & Regards, >> >> TC >> >
- Next message: Ralph: "Re: VB newbie - exposing VB subs to VBA?"
- Previous message: Lance Wynn: "Re: Custom Collection - NewEnum - Type Mismatch"
- In reply to: Ken Slovak - [MVP - Outlook]: "Re: Using Visual Studio Installer, create an Outlook COM component that can only be installed by an administrator but, once installed, runs for all users"
- Next in thread: Helmut Obertanner: "Re: Using Visual Studio Installer, create an Outlook COM component that can only be installed by an administrator but, once installed, runs for all users"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|