C#?
i have 11,000 rows of data going through....is this just too much for Xsl
I shouldnt' have thought so. This probably points more to a bug in the
code. First test - does it work for smaller volumes? Next: are you
doing anything deeply recursive in the xsl? A typical thing to look
for would be templates that call each-other (possibly itself) -
typically passing arguments (xsl:param, xsl:with-param) to enumerate a
sequence.
Likewise, the same things are possibly if you using script inside the
xslt (although this is less common).
I've used xsl on some pretty large fragments without issue. The other
thing to watch is that the overall structure needs to be better... you
can't get away with much laziness (//Something, just to save typing
the path, etc) - and proper consideration of indexing (xsl:key,
Muenchean grouping, etc), variable usage, etc gets more important.
Marc