I have a problem with the XslTransform looking as though it is not using my
custom XslResolver. My customer resolver has been working fine until I
tried to use the following in my style-sheet:
<xsl:variable name="codesFile"
select="document('D:\SorviveApps\XSL\RSNT_EDI_Xref .xml')" />
It seems as though the above statement is ignored even though I can see the
document path come through the customer resolver and no errors are
generated. The file is never brought in as the cross reference codes never
appear. This process works find in XML Spy just not when VB.Net is used to
perform the translation. The original XSL is loaded from a string brought
in from SQL Server but no errors are produced during the XSL.Load either.
Does anyone have any ideas how to get better visibility to what is going
wrong or how to do this?
Thanks,
Matt