Hello, 

Visual XSLT currently supports two XSLT engines, Xalan 1.0 (based
on Xerces C++), and the .Net System.Xml.Xsl engine.  Komodo
supports only Xalan 1.0.

Visual XSLT 1.5, which will go into beta *real soon now* supports
passing .Net objects to your extensions.  This means if you
can rewrite your VBScript code as VBScript.net (and I'm not
sure how much rewriting that will entail), you'll be able
to debug your XSLT scripts in Visual XSLT.  We haven't yet
implemented debugging the extensions scripts themselves from
within XSLT, but you'll be able to see the results.

Unfortunately, the C++-based version of Xalan doesn't support
extensions at all, so that means Komodo doesn't.

Regards,

Eric Promislow

On Fri, Jun 28, 2002 at 04:53:19PM +0200, Gert-Jan Bartelds wrote:
>  Hi all,
>   
>  I just downloaded eval versions of Komodo and Visual XSLT in order to find
>  out whether these tools could be useful for us in our company. We do a lot
>  of XML / XSLT development, but we feel we are still lacking in tool support.
>   
>  A significant number of our existing XSLT files use extension functions,
>  some of those extension functions are implemented in VBScript.
>   
>  I suspect Visual XSLT does not support these VBScript functions, because
>  there is no VBScript interpreter targeting the .NET runtime (please correct
>  me if I'm wrong).
>   
>  But does Komodo support VBScript extension functions??
>   
>  Thanks in advance,
>   
>  Gert-Jan Bartelds
>  Fenestrae BV
>   
>  moc.eartsenef@bnajtreg <mailto:moc.eartsenef@bnajtreg>    ( *reverse*
>  engineer to get the proper address)
>   
>   
_______________________________________________
Visual-XSLT-discuss mailing list
Visual-XSLT-discuss@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs