none
manifest download error appears for Outlook addin RRS feed

  • Question

  • we are using VSTO 2010,, our addin displays the folowing error message

    "The deployment manifest could not be downloaded because a connection to the network could not be established"

    the installer works fine. we install using vsto|local.

    the addin loads fine.

    and a few times QA got this error.

    the vsto file content:

    <?xml version="1.0" encoding="utf-8"?>
    <asmv1:assembly xsi:schemaLocation="urn:schemas-microsoft-com:asm.v1 assembly.adaptive.xsd" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" 
    xmlns:co.v1="urn:schemas-microsoft-com:clickonce.v1" xmlns:co.v2="urn:schemas-microsoft-com:clickonce.v2" xmlns="urn:schemas-microsoft-com:asm.v2" xmlns:asmv1="urn:schemas-microsoft-com:asm.v1" 
    xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:xrml="urn:mpeg:mpeg21:2003:01-REL-R-NS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <assemblyIdentity name="My.Addin.vsto" version="1.0.0.0" publicKeyToken="345lkj2h345lh234" language="neutral" processorArchitecture="msil" xmlns="urn:schemas-microsoft-com:asm.v1" />
    <description asmv2:publisher="Microsoft" asmv2:product="My.Addin" xmlns="urn:schemas-microsoft-com:asm.v1" />
    <deployment install="false" />
    <compatibleFrameworks xmlns="urn:schemas-microsoft-com:clickonce.v2">
    <framework targetVersion="4.0" profile="Full" supportedRuntime="4.0.30319" />
    </compatibleFrameworks>
    <dependency>
    <dependentAssembly dependencyType="install" codebase="My.Addin.dll.manifest" size="44556">
    <assemblyIdentity name="My.Addin.dll" version="1.0.0.0" publicKeyToken="345lkj2h345lh234" language="neutral" processorArchitecture="msil" type="win32" />
    <hash>
    <dsig:Transforms>
    <dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" />
    </dsig:Transforms>
    <dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
    <dsig:DigestValue>fnMzJRyfeCm66irE8dz+US3LdKusE=</dsig:DigestValue>
    </hash>
    </dependentAssembly>
    </dependency>
    <publisherIdentity .../>
    <Signature Id="StrongNameSignature" xmlns="http://www.w3.org/2000/09/xmldsig#">...</Signature>
    </asmv1:assembly>

    noteworthy: this has only been spotted on VM's since the addin is not yet deployed.

    any ideas what the Click-Once thinks is missing? why this would happen occasionally?

    Thursday, July 25, 2013 12:33 PM

Answers

  • Hi Yossi.YY.

    The deployment manifest file for Office solutions identifies the current version and other deployment settings. It references the application manifest, which describes the current version of the solution and all of the files that are contained in the solution.

    If this error happens but not consistently, you may need to rebuild and publish this addin again and try to set up the exe.

    Thursday, August 1, 2013 8:08 AM

All replies

  • Hi Yossi.YY.

    Could you please tell me which kind of way do you use for publishing?

    Here is a URL that own the same error.

    "http://social.msdn.microsoft.com/Forums/vstudio/en-US/43689a24-f9ed-45ef-9d46-f42269893591/vsto-clickonce-installation-fails-with-the-deployment-manifest-could-not-be-downloaded"

    According to above issue, the VM's proxy setting caused this error.

    After you checked by this way, if the error still happened,please let me know.

    Thanks.



    Friday, July 26, 2013 5:55 AM
    Moderator
  • Hi George

    as I mentioned, the install passes fine, and the add-in works. and also our manifest doesn't point to any URL!

    this error happens after a few days. and not consistently.

    Sunday, July 28, 2013 8:22 AM
  • Hi Yossi.YY.

    The deployment manifest file for Office solutions identifies the current version and other deployment settings. It references the application manifest, which describes the current version of the solution and all of the files that are contained in the solution.

    If this error happens but not consistently, you may need to rebuild and publish this addin again and try to set up the exe.

    Thursday, August 1, 2013 8:08 AM