Thanks for the reply!

#2 does not seem viable. See:
http://stackoverflow.com/questions/2882963/xslt-adding-elements-on-the-s
ame-path

I edited the IL code of the WixUtilExtensions.dll. I'd happily just
recompile the WiX source code, but that requires 1GB of SDK and I'm
still in the process of downloading it... But I think I'll eventually do
that. I'd be happy to contribute it back, but I'm not sure what you mean
by that (committing to source control?).

-----Original Message-----
From: Blair [mailto:os...@live.com] 
Sent: Monday, May 24, 2010 7:13 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Using document() function in XSLT with HEAT

The three solutions in order of speed are:
1. Edit/recompile WixUtilExtension.dll to enable the document() XSLT
function. (Source file appears to be UtilTransformMutator.cs)
2. Change your transform to eliminate the use of the Document function.
3. Open a bug with the WiX team to enable the document() XSLT function.

If you do #1, please consider contributing it back. If either #1 or #3
are
done, please consider also turning on the EnabledScript property. The
easiest way to do both is to simply pass the static
XsltSettings.TrustedXslt
property to the Load method.

-----Original Message-----
From: Chrobot, Stefan [mailto:stefan.chro...@sabre.com] 
Sent: Monday, May 24, 2010 2:35 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Using document() function in XSLT with HEAT

Hello,

 

I get this error message:

 

"heat.exe : error HEAT5055 : Error applying transform <file.xslt> to
harvested WiX: Execution of the 'document()' function was prohibited.
Use the XsltSettings.EnableDocumentFunction property to enable it. An
error occurred at.."

 

Is there a way to quickly workaround this issue?

 

------------------------------------------------------------------------------

_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to