views:

869

answers:

5

I'm having some issues deploying a visio addin. running the VSTO file works on my computer, but whenever i try and move it to any other user's computer it throws an error on deployment. I thought it might be a setting i'd set in the porject properties so i created an entirely new plugin project and set it to display a message box on startup. The error i'm getting is "the expected element "addin" was not found in the xml"

deployment error

+2  A: 

This is caused by an issue with Clickonce. I found a workaround by installing the addin using MSI. This Guide was a lot of help.

Taken from the section about registry settings for the msi installation:

It is important to note the ‘|vstolocal’ value appended to the end of the Manifest value. This informs the VSTO runtime that it is locally installed and to not invoke the ClickOnce installer.

zeocrash
+1 this an annoying road bump during one deployment.
Anonymous Type
A: 

This is an issue with the version of Visio your add-in targets versus what is installed on the client machine. AddIn is an element that is new with the 2007 versions of Office. More than likely the client is running Visio 2003.

GabeH
that was not the case. We do not have visio 2003 on our systems
zeocrash
the part to focus on is not the version it could potentially have happened with 03 or 07, the invalidmanifestexception means the problem is with a manifest file, most likely the app.vsto. In this case it was config of the msi.
Anonymous Type
A: 

Hi,

I'm having the same issue with our Word, Excel, Outlook and PowerPoint add-in. The installation of the msi runs perfect. When starting Word for example, the Add-in itself gets 'installed' and then I receive the error. I have added |vstolocal to the registry, which is located in the HKCU tree.

The projects is a Visual Studio 2010 project, build on TFS 2008. The installation on an Office 2010 goes well, the error only occurs when Office 2007 is on the machine.

Anything else I'm overseeing?

Joeri
Found the solution. Seems that I need to install Visual Studio 2010 Tools for Office Runtime. That fixed the issue.
Joeri
A: 

Hi,

I'have the same problem...my project was created in Visual Studio 2008 and now imported in Visual Studio 2010. The installation works fine with Office 2010 but not with Office 2007.

Have you resolved the problem ??

Thank you

hannibal10
A: 

The solution to my experience with this issue was the one given by Joeri on the 8th July - install Visual Studio 2010 Tools for Office Runtime on the target machine.

Peter
his problem and the one in the question are different
zeocrash
Yes, I guess I was in a similar boat to the one s/he was in - i.e. I was looking for a solution to a problem and the search engines gave this post as a possibility. The problem that you were having was not exactly the same, but the solution that Joeri suggested was what helped me solve my problem, so I just wanted to acknowledge that as a useful suggestion in case anyone else like me (and Joeri) came along with a simliar problem with the same solution - i.e. the need to deploy the VS 2010 Tools for Office Runtime.
Peter