Outlook 2003 AddIn Deployment

Please help end this hideous nightmare I am having with the deployment of an Office 2003 Outlook Addin.
Developed using VS2005. I have been through all the posts and still cant get the thing to work.
The messageboxes dont get displayed when Outlook starts, no error messages or error entries
in the event log.
-----------------------------------------------------------------------------
Lots of points to be had if you can help me sort this one!!
-----------------------------------------------------------------------------

I have created a shared addin (Other project Types -> Extensibility -> Shared Add-in )

There is no code apart from two message boxes in the "OnStartupComplete" and "OnConnection" events
to show that the addin. The code has been signed with a strong name.

I have the following components installed on the target machine (see attached image):-

1) .NET Framework 2.0,
2) .NET Framework 2.0 SDK,
3) VSTO SE Runtime,  (manual install)
4) Office 2003 Interop Assemblies (manual install)

LoadBehaviour is set to 3 in the registry.

-----------------------------------------------------------
Security
-----------------------------------------------------------

I have run the following command to set the security policy on the target machine:-
Runtime security Policy -> User Policy Nod -> Code Groups -> All_Code
New group :-

Name = "Addin Projects"
Description = "New code group for Add-in Projects"
Choose condition type for this group = "Strong Name"
Imported the addin DLL then selected "Full Trust"

Any help would be much appreciated.

imports Extensibility
imports System.Runtime.InteropServices
Imports System.Windows.Forms

#Region " Read me for Add-in installation and setup information. "
' When run, the Add-in wizard prepared the registry for the Add-in.
' At a later time, if the Add-in becomes unavailable for reasons such as:
'   1) You moved this project to a computer other than which is was originally created on.
'   2) You chose 'Yes' when presented with a message asking if you wish to remove the Add-in.
'   3) Registry corruption.
' you will need to re-register the Add-in by building the $SAFEOBJNAME$Setup project, 
' right click the project in the Solution Explorer, then choose install.
#End Region

<GuidAttribute("B20BB3CB-DD3E-435E-B0F2-E521D7F37F1C"), ProgIdAttribute("Vanilla.Connect")> _
Public Class Connect
	
	Implements Extensibility.IDTExtensibility2

	Dim applicationObject as Object
        Dim addInInstance as object
	
	Public Sub OnBeginShutdown(ByRef custom As System.Array) Implements Extensibility.IDTExtensibility2.OnBeginShutdown
	End Sub
	
	Public Sub OnAddInsUpdate(ByRef custom As System.Array) Implements Extensibility.IDTExtensibility2.OnAddInsUpdate
	End Sub
	
    Public Sub OnStartupComplete(ByRef custom As System.Array) Implements Extensibility.IDTExtensibility2.OnStartupComplete
        MessageBox.Show("OnStartupComplete", "Debug", MessageBoxButtons.OK, MessageBoxIcon.Information)
    End Sub
	
	Public Sub OnDisconnection(ByVal RemoveMode As Extensibility.ext_DisconnectMode, ByRef custom As System.Array) Implements Extensibility.IDTExtensibility2.OnDisconnection
	End Sub
	
	Public Sub OnConnection(ByVal application As Object, ByVal connectMode As Extensibility.ext_ConnectMode, ByVal addInInst As Object, ByRef custom As System.Array) Implements Extensibility.IDTExtensibility2.OnConnection
		applicationObject = application
        addInInstance = addInInst

        MessageBox.Show("OnConnection", "Debug", MessageBoxButtons.OK, MessageBoxIcon.Information)

    End Sub

End Class

Open in new window

installed-apps.JPG
setsecurity1.JPG
setsecurity.JPG
ashleyfoAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

xenacodeCommented:
Hi,

If you are using VSTO SE and VS 2005 for an Office 2003 solution then you don't want to create a shared addin, you want to create a VSTO add-in. Choose the project type in the attached screenshot.

Instead of a Connect class you will get a ThisAddIn class with a StartUp event.

You also get a setup project created automatically.

Pete
Xenacode Ltd
Addin.JPG
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ashleyfoAuthor Commented:
Marvellous
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Programming

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.