Hi Smbolster,

Yes, the client do have SP1 or higher. Have already checked whether outlook
has disabled the add-in, nothing there. I have entered a key for the
project. The registry loads perfectly on the client machine but the add-in
is just not there. I have checked all possible things..or let's say all
obvious things but now i'm not sure where to look next.

Thanks for your help and advise thus far.

Regards
PJerling

" wrote:

Does the client have sp1 or higher?

In help == about == disabled items is there anything in there?
These will usually show up in the com-addins without a check but you
never know.

Did you add a key in the Add-in project?

Just a few things to look at, other than that I'm not really sure
which way to head.

On Oct 26, 8:41 am, pjerling
wrote:
Hi Smbolster,

Yes, I have installed VSTO Runtime on the client machine. The only reason
why I tried to manually install it was to see whether it would work. I am
missing something!

I have the SetSecurity solution in my code and have set the required
permission etc.

Any ideas?

Thanks for your reply.

" wrote:
Have you installed the Visual Studio Tools for Office runtime on the
client machine?

Outlook will not see the dll created by VS as a valid com add-in when

trying to add it manually.

On Oct 26, 4:17 am, pjerling
wrote:
Hi there,

Created a 2003 Office Outlook Add-in using Visual Studio .NET 2005. When
installing the add-in on a non-development machine it appears that the add-in
is not appearing in the Com-Add-ins. I then tried to manually add the
add-in. But when I try to do that I receive the following error message...

path.dll is not a valid Office add-in.

Where do I go from now?