Hello,

I'm currently developing an Outlook Add-in with Visual C# 2005 Express. It
loads and run on my development machine but it does not on any other machine,
and Outlook changes LoadBehavior property on my registry from 3 to 2.
I've coded an Add-in from scratch (on another machine) , an empty Outlook
Add-in that shows a popup box on OnConnect method, but it also loads and run
on the development machine.
Basically, I think that the problem is that any Add-in only runs on the
development machine.

Has anyone the same problem?
Any suggestions?

Regards,

Bernat.

Oh, I installed the following in the client machine and development machine.

* Windows XP
* Microsoft Office 2003
* MS PIA
* lockbackRegKey.msi
* extensibilityMSM.msi

And yes, I've written all the registry entries needed for the Add-in to work
and on the development machine I'm installing the Add-in using NSIS
installing software, i mean that i'm not running it through the debugger.

Did you make sure to deploy any other dependencies you might be using? The
most common missing one on a machine that doesn't have VS installed is
stdole.dll.

--
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


"bernat" wrote in message
...
Oh, I installed the following in the client machine and development
machine.

* Windows XP
* Microsoft Office 2003
* MS PIA
* lockbackRegKey.msi
* extensibilityMSM.msi

And yes, I've written all the registry entries needed for the Add-in to
work
and on the development machine I'm installing the Add-in using NSIS
installing software, i mean that i'm not running it through the debugger.

I've deployed all dependencies on my client machine, including stdole.dll but
the add-in doesn't load.
When I open Outlook on my client machine, the Add-in doesn't execute the
OnConnection method and changes the LoadBehavior from 3 to 2 on the registry.
Every time I change the LoadBehavior to 3 and then execute Outlook, it
changes the property to 2.
I'm not using VSTO, instead, I've written the Add-in from scratch,
implementing Extensibility.IDTExtensibility2 and writing all registry keys
needed for the add-in to work.
Today i've been developing a simple/dummy outlook addin on the client
machine, the add-in shows a popup box when outlook starts, and it works! but
it works only on the developing machine. If I put this simple/dummy addin on
my original machine, it doesn't load nor run.
No matter the complexity of the add-in, for me, an outlook add-in only runs
on the development machine.


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

Did you make sure to deploy any other dependencies you might be using? The
most common missing one on a machine that doesn't have VS installed is
stdole.dll.

--
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


"bernat" wrote in message
...
Oh, I installed the following in the client machine and development
machine.

* Windows XP
* Microsoft Office 2003
* MS PIA
* lockbackRegKey.msi
* extensibilityMSM.msi

And yes, I've written all the registry entries needed for the Add-in to
work
and on the development machine I'm installing the Add-in using NSIS
installing software, i mean that i'm not running it through the debugger.

I'm wondering if that's due to using VS Express rather than the full-blown
version. I recall something about limitations of VS Express. According to
the feature comparisons at
http://msdn2.microsoft.com/en-us/express/aa700921.aspx addins aren't
supported by VS Express, so that might be the problem.

FWIW, I've never had any problems deploying extensibility addins for Outlook
as long as the requirements were installed on the target computer. It's not
like with VSTO, which can make deployment a real chore.

If OnConnection isn't being fired it's one of 2 things:
missing prerequisites or requirements or limitations in the Express
package.

--
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


"bernat" wrote in message
...
I've deployed all dependencies on my client machine, including stdole.dll
but
the add-in doesn't load.
When I open Outlook on my client machine, the Add-in doesn't execute the
OnConnection method and changes the LoadBehavior from 3 to 2 on the
registry.
Every time I change the LoadBehavior to 3 and then execute Outlook, it
changes the property to 2.
I'm not using VSTO, instead, I've written the Add-in from scratch,
implementing Extensibility.IDTExtensibility2 and writing all registry keys
needed for the add-in to work.
Today i've been developing a simple/dummy outlook addin on the client
machine, the add-in shows a popup box when outlook starts, and it works!
but
it works only on the developing machine. If I put this simple/dummy addin
on
my original machine, it doesn't load nor run.
No matter the complexity of the add-in, for me, an outlook add-in only
runs
on the development machine.

Hello,

as I know you should create a COM Shim for a .Net Extensibility AddIn.
Thats a native COM wrapper for your .Net AddIn.

See
http://blogs.msdn.com/mshneer/archiv...udio-2005.aspx
Download:
http://www.microsoft.com/downloads/d...displaylang=en

Also make sure that on the Target machine there is no other .Net Addin wich
maybe causes problems by referencing another framework version (1.1)

Hope this helps,
greets, Helmut




"bernat" schrieb im Newsbeitrag
...
I've deployed all dependencies on my client machine, including stdole.dll
but
the add-in doesn't load.
When I open Outlook on my client machine, the Add-in doesn't execute the
OnConnection method and changes the LoadBehavior from 3 to 2 on the
registry.
Every time I change the LoadBehavior to 3 and then execute Outlook, it
changes the property to 2.
I'm not using VSTO, instead, I've written the Add-in from scratch,
implementing Extensibility.IDTExtensibility2 and writing all registry keys
needed for the add-in to work.
Today i've been developing a simple/dummy outlook addin on the client
machine, the add-in shows a popup box when outlook starts, and it works!
but
it works only on the developing machine. If I put this simple/dummy addin
on
my original machine, it doesn't load nor run.
No matter the complexity of the add-in, for me, an outlook add-in only
runs
on the development machine.


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

Did you make sure to deploy any other dependencies you might be using?
The
most common missing one on a machine that doesn't have VS installed is
stdole.dll.

--
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


"bernat" wrote in message
...
Oh, I installed the following in the client machine and development
machine.

* Windows XP
* Microsoft Office 2003
* MS PIA
* lockbackRegKey.msi
* extensibilityMSM.msi

And yes, I've written all the registry entries needed for the Add-in to
work
and on the development machine I'm installing the Add-in using NSIS
installing software, i mean that i'm not running it through the
debugger.

Hi Helmut

Although if there are no other addins or none creating a problem the addin
should load and run with no problems even without a shim.

--
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


"Helmut Obertanner" wrote in message
...
Hello,

as I know you should create a COM Shim for a .Net Extensibility AddIn.
Thats a native COM wrapper for your .Net AddIn.

See
http://blogs.msdn.com/mshneer/archiv...udio-2005.aspx
Download:
http://www.microsoft.com/downloads/d...displaylang=en

Also make sure that on the Target machine there is no other .Net Addin
wich maybe causes problems by referencing another framework version (1.1)

Hope this helps,
greets, Helmut