I just tested this package on a site I am developing, and it was working fine until I decided to implement XsltResult on some transformations I had previously used macros with attached xslt file for.
Now usage of the XSltResult control results in a System.Web.AspNetHostingPermission security exception and I can't figure out why this is.
The website is running in full trust, pages using masterpages without xsltresult controls displays fine and if I remove the xsltresult controls from the masterpage it displays without problems.
Does the user your app pool is running under have Read & Execute, List and Read permissions to the framework dir and full control to the temporary asp.net files directory under that and full control to %TEMP%?
All was runnnig well with one xsltresult control, until suddenly after adding some more xsltresult controls, and deploying the site from vs project to local machine, I had the security issue.
It went away after switching the app-pool to run as networkservice, adding network service to acl, and restarting app-pool, so it's probably related to some setup issue on my dev-workstation. Sorry to have bothered you :-s
Security exception
I just tested this package on a site I am developing, and it was working fine until I decided to implement XsltResult on some transformations I had previously used macros with attached xslt file for.
Now usage of the XSltResult control results in a System.Web.AspNetHostingPermission security exception and I can't figure out why this is.
The website is running in full trust, pages using masterpages without xsltresult controls displays fine and if I remove the xsltresult controls from the masterpage it displays without problems.
Any idea what is going on?
Regards
Jesper Hauge
Does the user your app pool is running under have Read & Execute, List and Read permissions to the framework dir and full control to the temporary asp.net files directory under that and full control to %TEMP%?
All was runnnig well with one xsltresult control, until suddenly after adding some more xsltresult controls, and deploying the site from vs project to local machine, I had the security issue.
It went away after switching the app-pool to run as networkservice, adding network service to acl, and restarting app-pool, so it's probably related to some setup issue on my dev-workstation. Sorry to have bothered you :-s
Regards
Jesper Hauge
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.