Hi Sean
We tried to address the issue with Windows Azure Website with no luck, and reported it to the Windows Azure team, but it hasn't been addressed yet. Hard to say what is exactly the issue, it could be something related to the network configuration on the virtual machines that host WAW-s ( For more info see my answer here: http://stackoverflow.com/questions/22900225/phantomjs-as-web-job-in-azure ).
To render function previews, we run a console application /App_Data/Composite/PhantomJs/phantomjs.exe.
At the moment we found those cases when it doesn't work:
1) When the user account, running the website, does not have a read access to the disk root. (f.e. C:\ if hosted on drive C)
2) There could be some network restrictions or misconfiguration, so PhantomJs can't do the rendering.
3) When hosted on IIS 8 (Windows 8+/Windows Server 2012+) PhantomJs seem to create its temporary files on drive "C:\Ofi Labs\PhantomJs" instead of WIndow's users's AppData folder. - there could be an issue if NTFS permissions are missing (we haven't addressed this issue yet).
We tried to address the issue with Windows Azure Website with no luck, and reported it to the Windows Azure team, but it hasn't been addressed yet. Hard to say what is exactly the issue, it could be something related to the network configuration on the virtual machines that host WAW-s ( For more info see my answer here: http://stackoverflow.com/questions/22900225/phantomjs-as-web-job-in-azure ).
To render function previews, we run a console application /App_Data/Composite/PhantomJs/phantomjs.exe.
At the moment we found those cases when it doesn't work:
1) When the user account, running the website, does not have a read access to the disk root. (f.e. C:\ if hosted on drive C)
2) There could be some network restrictions or misconfiguration, so PhantomJs can't do the rendering.
3) When hosted on IIS 8 (Windows 8+/Windows Server 2012+) PhantomJs seem to create its temporary files on drive "C:\Ofi Labs\PhantomJs" instead of WIndow's users's AppData folder. - there could be an issue if NTFS permissions are missing (we haven't addressed this issue yet).