Page 1 of 1
MSXML.NET not available in oxygen 8.0
Posted: Tue Jan 16, 2007 8:19 pm
by Wabiloo
Hi!
Before I updated to oxygen 8.0, I had an MSXML.NET transformer that was able to take XSLT 2.0 stylesheets.
In the "Edit scenario" dialog, MSXML.NET is not in the Transformer list anymore. I've tried using .NET 2.0 instead, but I get an error message when transforming telling me that the transformer is not compatible with XSLT 2.0...
Any idea what is going on?
Posted: Wed Jan 17, 2007 9:50 am
by george
Hi,
There is some confusion here. There is no Microsoft processor with support for XSLT 2.0, probably you used Saxon.NET? That is deprecated since some time because the development was taken over by Saxonica and the .NET version of Saxon is available from Saxonica website. This is basically the same code as Saxon 8 translated in .NET.
Currently it should be possible to integrate it as an external processor but you can very well use the Saxon8B which is the Java version that is the base for the .NET port.
Best Regards,
George
Posted: Wed Jan 17, 2007 2:25 pm
by Wabiloo
OK, never mind that. I now changed my XSL to 1.0 format.
I still however do not see MXSML.NET in the Transformed drop-down box when editing the scenario.
It was definitely in my v6.0 and v7.0 of Oxygen. My colleague also uses 6.0 and has that choice...
That's where my problem is...
Posted: Wed Jan 17, 2007 3:59 pm
by sorin_ristache
Hello,
oXygen version 7.0 introduced the MSXML.NET 2.0 transformer. The MSXML.NET transformer that was available in versions 6.x was called .NET 1.0 in the Transformer combo of the Edit scenario dialog and the new transformer was called .NET 2.0. They are Microsoft transformers and they do not support XSLT 2.0. You can test that by trying to run a stylesheet that uses XSLT 2.0 features with the MSXML.NET transformer available in oXygen 6.2 or with the .NET 2.0 one available in oXygen 7.0 and later.
Regards,
Sorin