ramiramilu's answer is actually not correct. You can run any exe you want (check this for example). The problem you are hitting is not in running an exe, it's something specific to wkhtml2pdf.exe
itself. That exe uses a bunch of GDI+
calls on Windows for rendering the PDF and that is what's not allowed in Azure Websites sandbox (the GDI+
calls, not running an exe).
Using a WebJob won't help either because WebJobs run in the same context as the site which means under the same sandbox.
Edit:
There is nothing special to how you would launch an external process on Azure Websites than how you would do it normally with C#. Again the problem you are facing is with wkhtml2pdf.exe
and not with the general concept of launching a process.
Here is a sample that you can try that launches cmd.exe
and reads what is written on stdout
var processStartInfo = new ProcessStartInfo()
{
Arguments = "/c echo "test"",
FileName = @"c:windowssystem32cmd.exe",
RedirectStandardOutput = true,
UseShellExecute = false
};
var process = Process.Start(processStartInfo);
using (var streamReader = new StreamReader(process.StandardOutput.BaseStream))
{
ViewBag.MessageFromExe = streamReader.ReadToEnd();
}
ViewBag.MessageFromExe
will have the value "test"
you can verify that on your view and you can run that just fine in Azure Websites
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…