|
|
Rank: Newbie
Groups: Member
Joined: 10/23/2014
Posts: 2
|
I'm using v6.0.36 of eo.pdf.
When rendering an mvc view to a pdf using the RenderAsPDF attribute we are getting a HIPS alert on it trying to access the following.
C:\Windows\system32\config\systemprofile\AppData\Local\
C:\Windows\system32\GDIPFONTCACHEV1.DAT
If possible we would not like to add rules to allow the IIS site to access these folders. Is there anything we can do to get around it.
On another site we are using v6.0.18.2 and we did not have to add this rule. The view on this site is rendered using the same attribute. I can't use this version on the new site due to it not supporting MVC5.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Hi,
This does not have anything to do with MVC5. All version of EO.Pdf needs access to your windows system directory (read only). So you must have that regardless of EO.Pdf versions.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 10/23/2014
Posts: 2
|
Thanks for the response.
After further investigation the exception rule is thrown because the later version has attempted to modify under the windows system directory. The site that works on the older version has read to windows but certainly not modify.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
No. We are not aware that our product would modify anything under Windows system directory. In fact most of our users run our product in a Web application and a web application absolutely should not have permission to write windows system directory.
We do write in the current user's temp directory. So you may want to check whether somehow you have your temp directory set to your system directory.
|
|