Hello - as we're having startup issues when deploying EO-PDF versions after v22.1.94 to AppServices, I upgraded to v23.0.83 to check whether our issues were resolved - we are calling EO-PDF from .NET Core 3.1. When we run our (web) application to generate PDF's locally we are hanging on the HtmlToPdf.ConvertHtml(...) call indicated
Code: C#
EO.Base.Runtime.EnableEOWP = true;
HtmlToPdf.MaxConcurrentTaskCount = 4; //** set to 16 or higher for User-Acceptance / Production
...
HtmlToPdfResult htmlToPdfResult = null;
using (var debugConsoleLog = new StringWriter())
{
HtmlToPdf.DebugConsole = debugConsoleLog;
using (System.IO.MemoryStream stream = new System.IO.MemoryStream())
{
try
{
htmlToPdfResult = HtmlToPdf.ConvertHtml(inputHtml, stream); //**hanging here**
}
catch (Exception ex)
{
_logger.LogError(ex, $"{this.GetType()}");
throw;
}
bytes = stream.ToArray();
}
debugConsoleLog.Flush();
}
var reader = new PdfDocument(new MemoryStream(bytes));
pageCount = reader.Pages.Count;
Nothing happens after this point and no error message is returned (no timeout, etc in the EO-PDF logging - nothing either in the Windows Event log)
Thinking it may be something within my local environment (eg. virus protection, etc), I deployed to our development slot on AppServices and still get the same behavior (hanging - no error message)
When I downgrade from EO-PDF v23.0.83 -> v23.0.51, the PDF generates both locally and when deployed to our development AppServices slot
Is the setup/configuration different for v23.0.83 ?