I think that in 9.0 the only way you can achieve this is to declare your function to expect instances of the native Saxon node interface, net.sf.saxon.om.NodeInfo.
I'm not sure I would recommend this: why is it necessary? Manipulating nodes is generally easier to do in XPath than in .Net languages like C#.
Michael Kay

From: saxon-help-bounces@lists.sourceforge.net [mailto:saxon-help-bounces@lists.sourceforge.net] On Behalf Of Ryan Puddephatt
Sent: 29 April 2008 19:02
To: saxon-help@lists.sourceforge.net
Subject: [saxon] Creating a .Net Extension function


                I’m trying to create an extension function in .Net, I want to pass a nodeset from XSLT into the function a return a sequence of strings, could someone point me in the right direction of the type I should expect Saxon to pass in and what it would expect me to return







Ryan Puddephatt

FIX Developer

Fidessa LatentZero

1 Alfred Place

London WC1E 7EB

t: +44 (0) 20 7323 6112

b: +44 (0) 79 8539 2458

f: +44 (0) 20 7462 4242

e: rpuddephatt@latentzero.com

w: http://www.latentzero.com


The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

This e-mail has been scanned for viruses by Verizon Business Internet Managed Scanning Services - powered by MessageLabs. For further information visit http://www.mci.com