I have a word vsto project. I signed the manifest with a test certificate, using the reate tewst certificate button in the Signing tab of the project propertie. After installing the vsto on the server, I used a custom made application that call the vsto and try to bind some data on it. However I have the Customized functionality in this application will not work because it has not been granted trust exception that shows in the event viwer and there is no data bound in my document.
I use VS2010 to create the projet and its for Word 2007.
Any ideas?
Thank you
Related
I have an VSTO Outlook Add-in which uses some WPF components. I have some problems on WPF components to be rendered correctly. For example, some objects are shown more bigger, etc. I have found a possible solution described here when you mix winform and wpf components. May I guess VSTO Outlook addin in fact are winforms? So I need to specify some configuration in an app.manifest file and I do not know how to create the manifest file. I don't know if the process to create it is the same as a normal winforms app or in case of an Outlook VSTO Add-in is different.
In the link I provided above it is explained to add some setting in the assemblyinfo.cs file, ok there is no problem with it, i have done it, but now I do not know how to add some settings to the app.manifest file. I have seen in the \bin\release folder I have an myAddin.dll.manifest but this file is created automatically when you build the Add-in so i guess i cannot touch it because if so it will be overwritten again when I do a new build/rebuild of my add-in. Also the content within myAddin.dll.manifest, from where is taken?
Please could you indicate me the steps i must follow?
UPDATE:
This link says application manifest file is created automatically, as I was guessing.
Application manifests are created automatically as part of the build
process.
So is there any way to create a post-build action to add a custom setting to application manifest?
One possibility would be to modify the manifest MyAddin.dll.manifest after build process suceed but i would like to automate it. Also i am wondering if there is the possibility to create an additional manifest file and Visual Studio merge it with the default one during the building process.
VSTO add-ins are not standalone applications like Windows Forms. The manifest file is created per-application, not add-in. So, the best what you could do is to create a manifest file for the host application which is Outlook in your case. The manifest file should be named in the following way:
Outlook.exe.manifest
and should be placed to the same folder with Outlook.exe application.
So, if you need to make changes with a manifest file they will be applied to the whole host application (Outlook) and have impact on all add-ins, not only yours.
The manifest works on the application level (exe), but VSTO addins are dlls hosted by outlook.exe, and you cannot add or update its manifest.
I'm working on a outlook web-addin. The addin works when in run it on local host, can see the addin in outlook.
When the manifest file is validated with "npm run validate", it looks fine. But when I try to import the manifest file using Excel Web -> Insert -> Office Add-ins, I get "Your Addin manifest is not valid" error. could some on please guide how to identify the issue.
I'm planning to host the web UI in azure and install the manifest file on my team mate's machine to run some tests.
You need to use the target host application for sideloading the web add-in. In your case this is Outlook. Also you may consider deploying centralized, see Deploy add-ins in the Microsoft 365 admin center for more information.
You may also find the Deploy and install Outlook add-ins for testing article helpful.
If it is a outlook addin, you should import it using outlook not Excel.
I have a C# Visual Studio 2013 solution (FindAlike) consisting of a number of projects. One of these projects (SimilarFiles) is a class library, including an AddIn Express component, as it implements an MS Office Add-in. When I publish the project as a ClickOnce installer an MS Add-in, a folder is created in the projects Publish folder with the version number of the project containing many files with extension .deploy. Also in the folder above are a file called findalike.application and one called setup.exe. If I copy the contents of the Publish folder to a new machine I can install the MS Add-in by clicking on findalike.application, but I receive a warning about an unknown publisher. If I confirm installation it proceeds satisfactorily.
I have a valid code signing certificate purchased from Comodo, which I use successfully with SignTool to sign a Windows Forms self-extracting installer from another project in the solution.
The option to sign the ClickOnce Manifest in the SimilarFiles project is greyed out, presumably because SimilarFiles is a class library project.
I can specify a code signing certificate by right-clicking on the SimilarFiles project and hovering over the Add-in Express entry and then selecting Signing Options, but the warning message still appears when I attempt the installation on a new machine
How can I use the code signing certificate in order to indicate to the ClickOnce installer on the new machine that the manifest is signed?
Signtool does not work on the setup.exe file, stating that it is not a valid Windows executable. Neither does it work on findalike.application
There is a Signing area on the VS Publish form which I'd missed. If I browse for my Code Signing Certificate (.pfx extension) and select SHA-1 only it signs OK, and install proceeds without warning. Thanks to Add-In Express for this solution.
The error happens when Outlook 2007 VSTO addin is loading at startup. This Windows 7 PC is used by multiple domain users. The error happens only for some of those users. For other users the addin works fine. I assume the unfortunate users do not have some permissions but not sure to where to look at.
Please, help if you hit the same error in the past. Thank you.
The error details are as follows
System.Deployment.Application.InvalidDeploymentException: Exception reading manifest from file:///C:/Program%20Files%20(x86)/<Application folder>/My_OutlookAddin.vsto: the manifest may not be valid or the file could not be opened. ---> System.Deployment.Application.InvalidDeploymentException: Manifest XML signature is not valid. ---> System.Security.Cryptography.CryptographicException: SignatureDescription could not be created for the signature algorithm supplied.
at System.Security.Cryptography.Xml.SignedXml.CheckSignedInfo(AsymmetricAlgorithm key)
at System.Security.Cryptography.Xml.SignedXml.CheckSignatureReturningKey(AsymmetricAlgorithm& signingKey)
at System.Deployment.Internal.CodeSigning.SignedCmiManifest.Verify(CmiManifestVerifyFlags verifyFlags)
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
--- End of inner exception stack trace ---
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
--- End of inner exception stack trace ---
at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.GetManifests(TimeSpan timeout)
at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.InstallAddIn()
Thank you guys for your feedbacks. I have resolved the puzzle. Firstly, the answers for your questions are as follows. The add-in was installed using setup.exe created in VS 2010 setup project, i.e. it was not a ClickOnce installation. The Visual Studio Tools for Office app was installed on the target PC and also was one of the prerequisites of the setup project. I believe the problem was caused by add-in project's signing certificate and strong name key (snk) file. The certificate was a temporary one issued by a developer. The snk file was created using this temporary certificate. I assume the generated add-in manifest worked only for a certain domain group users. I did not figure this out. What I did was I replaced the temporary certificate with the new one that company recently bought and created a new snk file. However, after deployment, add-in stopped working for all users. The error message was the same. That was when I started to look into the add-in manifest file. What I found was the manifest file created with new certificate had a SHA2 encryption algorithm. But, the VS 2010 can handle only earlier SHA1 version because the highest Framework version that it can target is FW 4. The SHA2 can be used only with FW 4.5 and higher versions. The solution was to use a three years old SHA1 certificate and snk file that were used when the add-in was updated last time in 2013. I found them in the company source code repository. Even the certificate expired last year the add-in manifest still works. By the way, SHA1 encryption algorithm was deprecated from January 2016. Nowadays, all new certificates for signing application are issued with other algorithms like SHA2.
Do the users it's not working for have Visual Studio Tools for Office (VSTO) installed?
See this:
Outlook Add-ins installation
I am trying to install a custom Outlook add-in for the OWA, however when I attempt to install the XML manifest file I receive an error stating that the app isn't supported by the current version of Exchange Server.
There is not an XML file in the application folder by default, so in order to comply with the request for an XML, I changed the file extension of the Manifest file from .manifest to .XML.
The OWA custom add-in installer does not seem to recognize this as the correct file.
Which file should I use, or what am I doing wrong?
OWA can't run VSTO add-ins. Instead, you need to create a Mail App (so-called Outlook Add-in). See Get Started with Outlook add-ins for Office 365 for more information.