-----Original Message-----
From: Martin Honnen martin(_dot_)honnen(_at_)gmx(_dot_)de [mailto:xsl-list-
service(_at_)lists(_dot_)mulberrytech(_dot_)com]
Sent: Friday, September 1, 2017 10:47 AM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] Structuring templates
Are you aware that XslCompiledTransform supports extension objects as
well as inline code? If you encapsulate your C# code in a class and pass
that as an extension object with e.g.
https://msdn.microsoft.com/en-
us/library/system.xml.xsl.xsltargumentlist.addextensionobject(v=vs.110).as
px
when you run XSLT then you don't depend on inline script compilation and
execution and I think it should also solve the problem you have with
sharing the C# code.
Obviously that way you need to write and compile the C# separately
instead of having XslCompiledTransform doing it for the inline code, I
am not sure whether it is an option.
Yeah, I am constrained by the WIX toolset and it doesn't offer the facility
to pass the code in as a compiled library which I am certain you are correct
in that it would likely solve the issue. I wish xsl v1 and all of msxsl could
just
be banished:)
Thanks,
jlc
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--