Fix XslCompiledTransform to work better in partial trust environments
XslCompiledTransform doesn't fully function in partial trust environments because if the TrustedXslt enum is used at construction, and the file contains <msxml:script> blocks, then the script is compiled dynamically to the process identity's Temp directory (C:\Users\<app pool identity>\Local\Temp on most machines).
As it's compiled code, why not put it in the standard .NET Temporary Files directory, thus allowing it to function perfectly well in partial trust environments?
Benjamin Howarth
shared this idea
3 comments
-
Bug filed over at MS Connect: https://connect.microsoft.com/VisualStudio/feedback/details/776030/xslcompiledtransform-compilation-location-should-be-changed
You can close this one if you want. -
Good shout, thanks Damian.
-
Thanks for the feedback. The XslCompiledTransform class is owned by a different team so you may have better traction suggesting this item as a bug on http://connect.microsoft.com. Note however that ASP.NET medium trust is no longer guaranteed to provide application isolation and is thus not recommended (see http://support.microsoft.com/kb/2698981)
