Site hangs when a second worker process tries to create a PDF about tuespechkin HOT 5 CLOSED

Thank you for finding this. I tried copying the the bin folder before but as we know that causes the app pool to recycle, which can have adverse effects when not desired. I have an idea though, I'll try it out and if it checks out I will upload it.

from tuespechkin.

0.9.3.2 is hot off the presses; it now copies uniquely based on the base directory of the running app domain. I've also begun using GZip compression on the embedded assemblies, cutting the package size down by over half.

from tuespechkin.

Just tried the latest version and it works great, thanks!

I end up with a folder name like this "TuesPechkin0.9.3.2_x86_CWindowsMicrosoft.NETFrameworkv4.0.30319Temporary ASP.NET Filesrootaecc03447ef3384bassemblydl33f655eab45d12f5e_8f63cf01" I guess that the random named folder within Temporary ASP.NET Files is unique for that website/app pool? I've tried with 2 of the sites on the server and they produce different folder names so all seems good.

Just wondering whether the Windows/Temp folder is the best place for this as it's not really a temporary file? You've ruled out the bin folder for good reason but could it possibly sit in the root of the application? I'm sure there is probably some security issue with that though. Or how about just adding the wkhtmltox.dll file as a reference when the NuGet package is installed so it gets copied to the bin folder? I know it's an extra reference, just thinking aloud.

from tuespechkin.

Glad to hear it is working for you.

Adding it as a reference would be a breeze but it is not possible to add unmanaged assemblies as references. There is a lovely attribute called PreApplicationStartMethodAttribute and it allows one to specify a number of methods to call in an assembly before the application starts. I could stick that in the AssemblyInfo.cs file and be good to go for copying to bin, except it's .NET 4.0 and up only, and web application only.

Since there is no good way to get that thing into the bin folder without recycling the app pool, asking users to remember to copy it, or expecting users to properly manage post build and post publish events in their .csproj files, I'm settling for the temp folder. 👅

from tuespechkin.

Ah I see. Sounds like the temp folder is the way to go then.

It's still working great on our web server where 2 sites are using it, however I'm getting it hanging quite a lot on my local machine running under IIS. Will create a separate issue for this now, got a couple of other issues I'll add too.

from tuespechkin.