>I am experiencing another big slowdown in .NET. This time it is in regards to the Xsl transformation I am applying to the export to Excel.
>
>Last week, we exchanged some threads in regards to the ability for a .NET application to export its dataset to Excel in a native spreadsheet. My ExportToExcel() method is using the following to apply the Xsl transformation:
>
>
> loXslCompiledTransform.Transform(loXmlDataDoc, Nothing, loStringWriter)
>
>
>Well, during our tests, we had only two records. Today, I am trying to apply that against the data, where I have 826 rows in the dataset. We guess what! As it takes about 0.5 second per row, I am ending up with a browser timeout as it would take several minute for this Xls transformation process to complete. This makes this approach unnacceptable.
>
>Anyone could explain this behavior as to know why it takes so long for the Xls transformation to execute?
A SWAG:
Why XmlToCursor() Is Slower Than Yesterday? Thread #
1118771 Message #
1118899
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up