Yes, Saxon SA is supported in Oxygen as well. As far as drag and drop
support for future versions that would require comments from George
and Dr. Kay as with any architectural changes obviously changes would
need to be put into place for the debugger (if this is the portion
that changed, that is :)
I do know that VS.NET 2005 has a debugger for XSLT 1.0 via
System...Xsl and I have spoken with members of the team responsible
for this project about developing external support for projects such
as Saxon.NET which, at the time, they were quite enthusiastic about
but generally its not the ones writing the code that make those
decisions so I cant say for sure where that may lead too, if anything.
I still know quite a few people on that team from my days working
withing the Visual Studio organization but knowing people and finding
a way to get access to the hooks to the VS.NET debugger are obvious
two things that have little in common.
There are some proprietary tools (in the sense that they have a built
in processor and dont support anything else) in tools such as
Butterfly but beyind this I am at a loss at the moment to any
others... undoubtedly I have missed some and someone will chime on :)
On Apr 1, 2005 4:22 AM, Andrew Welch <ajwelch@...> wrote:
> > :) and coordinate but either way there is full out of the box
> > debug support in <oXygen/> for Saxon 8.x.
> Does that mean when Mike releases 8.3.1/8.4 you can just drop in it and
> debug with the new version - or do you need wait for a new release of
> the IDE?
> Are there any alternatives to oXygen and Sylus Studio?
> What about Saxon SA support?
> This SF.net email is sponsored by Demarc:
> A global provider of Threat Management Solutions.
> Download our HomeAdmin security software for free today!
> saxon-help mailing list
:: M. David Peterson ::
XML & XML Transformations, C#, .NET, and Functional Languages Specialist