Discussion:
Excel 2007 addin - An unexpected element "description" was found
(too old to reply)
Andrew Wiles
2009-08-19 15:37:03 UTC
Permalink
I am trying to create a standard install package for an Excel 2007 VSTO addin
built in Visual Studio 2009 - I do not want to use ClickOnce.

I am registering the addin in
HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\<MyAddinName> withe
registry entries for CommandLineSafe, Description, FriendlyName, LoadBehavior
and Manifest

I am deploying the manifest created by Visual Studio as part of the build
process (this is not part of the primary output for the project) but when the
addin attempts to load I get an error saying that the manifest is invalid.

Am I using the correct manifest or do I have to create a different one??
Andrew Wiles
2009-08-20 09:12:11 UTC
Permalink
I have found the answer to this question:

I need to install the .vsto file as the manifest refered to in the registry
(i.e. the key value for "Manifest" is the path to the .vsto entry created by
the ClickOnce build) The .manifest file then needs to be installed in a
folder /Application Files/<Application Name> under the install folder.

It would be really nice if the VSTO team took some time off from developing
product feature and put some effort into providing some good documentation
and procedures for deployment.....
Post by Andrew Wiles
I am trying to create a standard install package for an Excel 2007 VSTO addin
built in Visual Studio 2009 - I do not want to use ClickOnce.
I am registering the addin in
HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\<MyAddinName> withe
registry entries for CommandLineSafe, Description, FriendlyName, LoadBehavior
and Manifest
I am deploying the manifest created by Visual Studio as part of the build
process (this is not part of the primary output for the project) but when the
addin attempts to load I get an error saying that the manifest is invalid.
Am I using the correct manifest or do I have to create a different one??
Loading...