Hello, we are wanting to deploy our PDF generate services using EO.PDF onto AppServices - we have tried to use a .NET Framework version (v4.7) with the AppServices container to allow .NET Framework applications run within the AppServices slot but it has caused problems. We are using EO.PDF v18.3.46. Although we could get our service to generate PDF's using the tool, it wouldn't take long before we were getting "Child process not ready" and "Child process exited unexpectedly" - child processes needed to be closed down manually before it would the tool would respond. Further relevant setup as follows:-

EO.PDF v18.3.46
ASP.NET v4.7
Platform 64-bit
WEBSITE_LOAD_USER_PROFILE=1
EO.Base.Runtime.EnableEOWP=true
HtmlToPdf.MaxConcurrentTaskCount=4
eowp.exe is copied to the bin folder at compile-time
The 4 files EO.Pdf, EO.WebBrowser, EO.Base, EO.WebEngine included as references via NuGet

We have several environments each with their own App slot for our PDF API - it seems we can get one of the environments working (generating PDF) however, we could not get each environment's PDF API working at the same time - is there some configuration we are missing (eg. does EO.PDF require that app slots be further isolated in some way?). Note that because we have had problems we have our fallback which hosts our PDF API using VM's with the same setup running under standard IIS websites/app-pools

Can we have an overall recommendation of how our PDF API which utilizes EO.PDF be hosted inside AppServices as we want to get off the VM's and move in exclusively to AppServices - i.e.
- is the above configuration going to work under AppServices (is there further config required) ?
- do we need to migrate our PDF API application to .NET Core (which version is recommended) ?
- do we need to use a particular EO.PDF version (eg. latest v20.2.34) ?