The current Xml Namespace uses the .Net standard XSLT 1.0 processor.
I would like to see a XSLT functionality leveraging an alternative processor that supports XSLT 2.0 (Saxon.NET)
This could either be done as a separate Task, or by potentally defining a seperate xslt engine as an additional attribute to the existing tasks.
I would like to see a XSLT functionality leveraging an alternative processor that supports XSLT 2.0 (Saxon.NET)
This could either be done as a separate Task, or by potentally defining a seperate xslt engine as an additional attribute to the existing tasks.