c# - using document() function in .NET XSLT generates error

Question

I'd like to use embedded resources in my XSLT file, but while invoking 'document(...)' C# complains that "Error during loading document ..."

I'd like to use defined resources in XSLT file and get them by this: "document('')//my:resources/"...

How can i do that??

ex xsl:

<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:my="xslt-gruper-v1.2.xsl" exclude-result-prefixes="my">

     <my:resources>
      <one>tryb</one>
     </my:resources>

     <xsl:variable name="res" select="document('')/*/my:resources/("/>
</xsl:stylesheet>

How can i get access to such structure without exceptions in C#? I'll add that during static transform via ex. Opera everything works fine.

question from:https://stackoverflow.com/questions/65830962/how-to-transform-xml-string-using-xslt-stylesheet-linked-by-xml-stylesheet-href

Answer 1

<xsl:variable name="res" select="document('')/*/my:resources/("/>

The value of the select attribute is not a syntactically correct XPath expression. Every compliant XSLT processor must raise an error.

Solution:

Correct the above to:

<xsl:variable name="vRes" select="document('')/*/my:resources"/>

If there is still an exception raised, do read about the XsltSettings class.

Then create an instance of XsltSettings with this constructor, like this:

XsltSettings(true, false)

Do not enable scripting -- keep the second argument of the constructor as false.

Below is a more complete code snippet:

// Create the XsltSettings object with document() enabled and script disabled.
XsltSettings settings = new XsltSettings(true,false);

// Create the XslCompiledTransform object and load the style sheet.
XslCompiledTransform xslt = new XslCompiledTransform();
xslt.Load("sort.xsl", settings, new XmlUrlResolver());

Update: Another possible reason for an error is when the XSLT stylesheet is dynamically created in memory (doesn't come from file). In this case an XSLT processor typically cannot resolve the relative uri in document('').

In this last case the solution is to make the wanted element the content of an xsl:variable and to use the xxx:node-set() extension function to address this element.