Need to allow GDI+ access for running ReportViewer inside of Consumption plan in Azure Functions
Need to allow azure functions running in consumption plan (with easy scaling) to be able to use ReportViewer to generate PDF, Excel and Word exports. Only appears to be possibly available to be used with Azure Functions in App Service plan https://azure.microsoft.com/en-us/blog/pdf-generation-and-loading-file-based-certificates-in-azure-websites/
Hello, Azure Functions on Consumption plan runs in a sandbox documented here: https://github.com/projectkudu/kudu/wiki/Azure-Web-App-sandbox. Some PDF operations are allowed as described there. For those that are not allowed you’ll need an App Service plan.
Evaldas Dzimanavicius commented
Similar as Dave Archer, we have a service built using Aspose libraries (Cells, Pdf, Diagram). We are migrating our code to serverless, but due to the fact that Aspose libraries rely on System.Drawing.Common (which is not supported in Azure Functions) we cannot do that.
Radomir Mastalerz commented
We need this feature as well! +1
Spent a long time building a task runner in Azure Functions to run all our legacy background tasks that used to run as a Windows Service on a VM... everything works brilliantly, apart from Microsoft.ReportViewer... We really need this to be supported! Is there some kind of work-around that would allow me to run reportviewer to generate PDFs in an Azure Function?
Dave Archer commented
Yes, we are trying to use a combination of Aspose.Cells and Aspose.Pdf to generate reports via a Azure Function App. This would really help, as its currently failing.
Tilo Christ commented
Yes, we need to run a headless browser (PhantomJS) as part of our software. GDI required.
Helge Sundal commented
Yes, we need it also.
Ed Johnson commented
Message get otherwise on consumption plans is Microsoft.Reporting.WebForms.LocalProcessingException: An error occurred during local report processing. ---> System.ArgumentException: Parameter is not valid.\r\n at System.Drawing.Graphics.GetHdc()\r\n at Microsoft.ReportingServices.Rendering.RichText.LineBreaker.Flow() ....