ansaurus

Question

Answer 1

+5 A:

I'm assuming that by "resource file" you mean a regular resx that is compiled into the assembly. In which case, not directly from xslt; however, you could add an extension object and use a key-base approach, i.e.

<xsl:value-of select="resx:getString('noposts')"/>

The "resx" alias would be mapped (xmlns) to a uri that you use when creating your xslt wrapper in C#. For example, with the xmlns (in the xslt preamble):

xmlns:resx="myextnuri"

we can map that in C# via:

public class MyXsltExtension {
    public string getString(string key) {
        return "TODO: Read from resx: " + key;
    }
}

and attach this to the namespace:

XslCompiledTransform xslt = new XslCompiledTransform();
xslt.Load("xslt.xslt");
XsltArgumentList args = new XsltArgumentList();
object obj = new MyXsltExtension();
args.AddExtensionObject("myextnuri", obj);
using (XmlWriter writer = XmlWriter.Create("out.xml")) {
    xslt.Transform("xml.xml", args, writer);
}

We now have full control to inject managed code (as extensions) into our xslt.

Marc Gravell 2009-09-03 07:43:08

Great help. It worked!Thanks!

Vijay 2009-09-03 08:30:59

`msxsl:script` is yet another option.

Pavel Minaev 2009-09-05 11:09:42

I can't see how `msxsl:script` would provide access to resx; I'd love to see an example...

Marc Gravell 2009-09-07 19:56:47

Answer 2

+2 A:

You can load resources from an external file using the document() function:

<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"&gt;
    <xsl:output method="html" indent="yes"/>

    <xsl:template match="@* | node()">
      <html>
        <head>
          <title>Test</title>
        </head>
        <body>
          <p>
            <xsl:value-of select="document('resources.xml')/items/item[@id = 'no_posts']"/>
          </p>
        </body>
      </html>
    </xsl:template>

XML resource file:

<?xml version="1.0" encoding="utf-8"?>
<items>
  <item id="no_posts">There are no blog posts to display.</item>
</items>
</xsl:stylesheet>

0xA3 2009-09-03 07:47:56

ansaurus

tags:

views:

answers:

Making XSLT language independent

related questions