If I create a simple xslt stylesheet I can quickly test this in VS2005 by
pressing the "Show XSLT Output" button rather than running the whole solution.

If I then create a xslt stylesheet with some extended functions I have to
run the whole solution (adding the extension objects to the XsltArgumentList
when calling XslCompiledTransform.Transform). The "Show XSLT Output"
function does not work because it does not know where to find the extension
functions.

Is it possible to define the extension function objects somewhere in VS2005
so that "Show XSLT Output" would work in this situation, I find it very handy
to be able to do a quick test of a xslt stylesheet rather than having to run
the whole solution.


Regards

Peran,=20

The only way I have been able to perform this task is create my =
extensions in a script and include them for quick testing. This is a =
pain because you basically have to write you fuction twice but I found =
once I had a typical library I only have to change the include and the =
xmlns statements to switch between the two.

HTH,=20

Matt


[quoted text, click to view]
If I create a simple xslt stylesheet I can quickly test this in VS2005 =
by=20
pressing the "Show XSLT Output" button rather than running the whole =
solution.

If I then create a xslt stylesheet with some extended functions I have =
to=20
run the whole solution (adding the extension objects to the =
XsltArgumentList=20
when calling XslCompiledTransform.Transform). The "Show XSLT Output"=20
function does not work because it does not know where to find the =
extension=20
functions.

Is it possible to define the extension function objects somewhere in =
VS2005=20
so that "Show XSLT Output" would work in this situation, I find it =
very handy=20
to be able to do a quick test of a xslt stylesheet rather than having =
to run=20
the whole solution.


Regards