Deploying Application

[Sarah S]

I am trying to deploy my first Outlook application to
other desktops. Working w/ Outlook 9.0 and Windows 2000.
I have created the following registry entry:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addin
s\ConnectToOutlook.Connect]
"FriendlyName"="ConnectToOutlook.Connect"
"Description"="Farm Bureau Insurance Submit to Mobius from
Outlook."
"LoadBehavior"=dword:00000003
"CommandLineSafe"=dword:00000000


ConnectToOutlook is what I called the form, but it is
stored as ConnectToOutlook.Dsr Should the .Dsr extension
be on the first line instead of .Connect?

I also copied my .dll file to the other machine and
registered it. When I try and run, it gets my message
saying the application is running, but none of my other
code seems to be working.

Any suggesstions on what I have missed?

 

[Ken Slovak - [MVP - Outlook]]

Connect is correct.

It's impossible to say what isn't working without seeing your code and
without you doing some debugging. Can you run your debugger on a machine
where the code isn't working and make sure you are getting the On_Connection
event and that your startup code is running? If you can't do that you can
sprinkle messages in your code that pop up dialogs at critical points in
your code.

The standard template for Outlook COM addins is the ItemsCB COM addin (VB
6). It shows best practices for Outlook addins and workarounds for common
Outlook addin bugs. It can be found on the Resources page at
www.microeye.com.

FWIW, registering an addin in the HKLM hive is called an administrative
installation. The addin won't show up in the COM Add-Ins dialog in Tools,
Options and so can't be enabled/disabled by the user. Registering in HKCU
would allow those things.