Microsoft Document to PDF: Difference between revisions
Jump to navigation
Jump to search
(Created page with "==Word2Jasper== Please open the project in '''Visual Studio Community Edition 2019''' then find the following lines from the <code>ReportConversionAddIn\ReportConversionAddIn....") |
|||
| Line 15: | Line 15: | ||
==References== | ==References== | ||
* [https://www.plutext.com/ Handle Office (docx | * [https://www.plutext.com/ Handle Office (<code>docx,xlsx,pptx</code>) documents from Java] | ||
* [https://github.com/wasseydev/word-report-conversion/issues/1 Guideline required for Word2Jasper] | |||
* [https://github.com/wasseydev/word-report-conversion Word to Jasper Report] | |||
* [https://www.docx4java.org/downloads.html Docx4j Downloads] | * [https://www.docx4java.org/downloads.html Docx4j Downloads] | ||
* [https://www.docx4java.org/trac/docx4j Docx4j] | * [https://www.docx4java.org/trac/docx4j Docx4j] | ||
Revision as of 22:39, 18 January 2021
Word2Jasper
Please open the project in Visual Studio Community Edition 2019 then find the following lines from the ReportConversionAddIn\ReportConversionAddIn.csproj. You may comment out or delete following lines and save the file then Visual Studio Community Edition 2019 prompt you to reload the project configuration. Please confirm the reload. After that it will be automatically recreate the ManifestCertificateThumbprint. Hope it will fix your signing issue.
<PropertyGroup>
<SignManifests>true</SignManifests>
</PropertyGroup>
<PropertyGroup>
<ManifestKeyFile>ReportConversionAddIn_TemporaryKey.pfx</ManifestKeyFile>
</PropertyGroup>
<PropertyGroup>
<ManifestCertificateThumbprint>A1FE05DDA1DF10BA23B874A26E7BDF224282D192</ManifestCertificateThumbprint>
</PropertyGroup>