Following on what Richard wrote,

Without specific differences it's hard for me to comment.

Visual XSLT doesn't implement a transformation engine;  it simply
wraps the Xalan and MS System.Xml.Xsl engines (but not any of
the MSXML COM-based engines).  This might be an issue across
these engines.  What happens when you run your transformations
from the command-line?

- Eric Promislow
EricP@[...].com

On Thu, Nov 28, 2002 at 09:43:21AM -0800, Richard Lander wrote:
>  What were the different results?
>   
>  Let's guess that the IDs that generate-id() generated were different. I know that those ar
e different across MSXML3, 4 and system.xml (that's what Visual XSLT uses generally). there 
is nothing in the XSLT spec that really constrains the IDs in any way, other than that they 
must be unique/node in a document and that they must conform to the NAME production. There m
ay be other things, as I'm not looking at the spec, but that's the basic idea. Conformant pr
oducts do not need to produce the same IDs on multiple runs of the same transform against th
e same XML instance nor do they need to keep to the same ID generation scheme across version
s.
>   
>  Then again, if the ID generation issue is not your issue, please send source, transform an
d results ...
>   
>  Thanks,
>   
>  Rich
_______________________________________________
Visual-XSLT-discuss mailing list
Visual-XSLT-discuss@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs