We have encountered some issues with the creating of ConversionLog.xml during Converter.Convert
Multiple call to this Convert method causes “file already in use”-issues
Can you help us with a solution/options where creating of ConversionLog.xml is not included. We would like to disable the creating/usage of this ConversionLog.xml in our software.
We are converting different documents to PDF.
Snippet:
converter.Convert(() => new MemoryStream(), (convertedStream, fileType) => convertedStream.CopyTo(resultStream), options);
Options being: PdfConvertOptions
We have looked in out forums, where someone wanted the same with Pdf-family and Java - but that fix is not working for us.
@KokholmDk
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): CONVERSIONNET-6298
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
GroupDocs.Conversion for .NET doesn’t create any ConversionLog.xml file. Could you please share a sample project/application and steps to reproduce the issue?
Hi Talaw, thank you for your reply. This file actually gives us issues when running on Azure Function or other “low-code” runtimes, due to the Conversion needs write-permission and location of this file.
Would be lovely with the option to opt this one out. Write-permission and location of the file is not that obvious.
It is not that obvious where this file is located on the Filesystem. Gives us issues on Azure Function and also on App Service.
Do you know how to set the folder of this generated File?
Okay. Would be nice to be able to opt. that conversionLog.xml out, by configuration - if the implementation does not care about this file Also making sure, in multi-threaded apps, that file is not locked. In the current version we are issueing file already in use - exception. Software should probaly not break, in case of multiple updates to a log-file.
The issues you have found earlier (filed as CONVERSIONNET-6298) have been fixed in this update. This message was posted using Bugs notification tool by nikola.yankov
Also making sure, in multi-threaded apps, that file is not locked. In the current version we are issueing file already in use - exception. Software should probaly not break, in case of multiple updates to a log-file.