It was hanlding the error, but that still changed the loadbehaviour to "2",
so I added this, "If Exists(m_olOutlookApplication.ActiveExplorer) Then"
with the hope that preventing the error from happening may solve the problem.

VS 2005 SE(Visual Basic) are the development environment and language

This is instantiated in the "ThisApplication" class which hooks the
"StartUp" event. oAddIn = New OutlookAddIn(Me) and passed to the class below.

Public Sub New(ByVal oApp As ThisApplication)
Try
m_olOutlookApplication = oApp
m_olInspectors = m_olOutlookApplication.Inspectors
m_olExplorers = m_olOutlookApplication.Explorers
If Exists(m_olOutlookApplication.ActiveExplorer) Then
m_olContactFolder =
m_olOutlookApplication.ActiveExplorer.Session.GetD efaultFolder(Outlook.OlDefaultFolders.olFolderCont acts)
olContactFolder = m_olContactFolder
'm_olContactFolderItems = m_olContactFolder.Items
m_butNewEmailSyncToCS = Nothing
m_butNewEmailSendSyncToCS = Nothing

CreateMainCSToolbar()
CreateClientSpaceProperty()
AddSyncedCompNames()
Else
Return
End If
'Automatic_Login()
Catch ex As Exception
MsgBox("OutlookAddIn failed to initialize:" & vbCrLf & vbCrLf &
ex.Message)
Finally
End Try
End Sub

The add-in isn't really being disabled as you assume, the loadbehaviour is
just being set to "2" To debug the code, I usually just hit the run button
and visual studio launches outlook. This method don't produce the desired
results because I assume VS "handles" the problems. I usually deploy the msi
to another test machine to ensure its working as expected.

Andrew

"Ken Slovak - [MVP - Outlook]" wrote:

Is it just being disabled from loading or is it actually being disabled by
Outlook (where it would show up in the Disabled Items list)?

Most likely if LoadBehavior is just being set to 2 and the addin isn't being
disabled you're receiving an error and not handling it.

Now when ActiveSync or other such software starts Outlook it's starting it
in what's called "headless" mode, where there are no Explorers or Inspectors
(no UI). So how is your code handling that condition? Are you instantiating
an Inspectors collection and an Explorers collection and handlers for the
NewInspector() and NewExplorer() events? Those would tell you when UI was
added to Outlook.

You also need to tell us more about your code.

What language?

Are you using a different solution with the correct Outlook version
references?

Have you simulated an ActiveSync startup and run your code in the debugger?

Are you logging and receiving any errors?

What is your startup code?

Do you hit your OnConnection or Startup event handlers?

If it's managed code are you receiving any Fusion loader errors when your
addin is started up in that way?

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"Andrew" wrote in message
news
I have an outlook add-in for 2003 which works fine when Outlook is launched
by the user. However, when an external program such Active Sync launches
the
outlook process, the add-in's load behaviour in the registry changes to 2
and
does not change back when the Outlook is launched again by the user. To
fix
the problem I have to go to the registry and change the load behaviour
back
to 3 or click repair in the "Add/Remove" programs for the add-in. Is there
any way to get around this problem. I know in Outlook 2007 that does not
happen because I also developed the add-in for it.

Thanks,
Andrew