Using the Certification Path tab, you can view the path from the Creating a certificate yourself through Visual Studio I understand your frustation with this as I have just gone through something similar.Ī certificate is needed as you have already discovered but for it to be recognised as a valid the issuer of the certificate must be trusted and this is only accomplished by the Certificate Authority. You can grant full trust to the customization by using signing the manifests with a certificate, clicking the trust prompt, or installing the Office solution to the
says: " Although the document itself is trustedīy using the trusted locations, additional permissions are needed to trust the customization. The template has the correct _AssemblyLocation pathĪs I read it, the above No 6 and No 8 should be sufficient to have the solution working:. I don't know if the prerequsites (that are stated as prerequsites in the solution) are installed on client computer. HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\.NETFramework\Security\TrustManager The WorkGroup templates folder is a Trusted Location. The document file is copied to the Workgroup Templates folder. The VSTO application is copied to C:\\Program Files (x86). The template will be used with Microsoft Word 2010. net Framework 4.0 and is developed with VS 2010 The solution is not signed with any authenticated certificate. 
The solution is intended for click-once-deployment. Users get the following certificate error message when they are trying toĬreate a new document based on the template: 
I am having trouble deploying a VSTO Word 2010 template (document) solution. Again, I'm not sure this one is really a developer question, but again, I know I get the good answers here :-).
0 kommentar(er)
