Mar 20, 2009
We use a small bit of excel exporting code in our app code at work to export XML controls from our ASP pages into an excel format using the following code:
View 1 Replies
Public Shared Sub Export(ByRef xml As Xml, ByVal filename As String)
Dim response As HttpResponse = HttpContext.Current.Response()
This is all fine, except we've encountered a rather frustrating bug. If the XML control has a link in it then the export code is called again. We have a button which will say "Export to Excel" from the .aspx page which simply calls ExcelExport.Export(Xml1, "MyFileName") which is in a LinkButton click event.Here's the order of events based on the form submit (selecting filters)
So the user submits a form which loads up the XML control in a nice viewable XSLT page. Then they click "export to excel" which will give them the page in excel instead, then they click on the XSLT page, for example a link, but the save dialog for excel comes up again. We've gone through the series of events, and if we do not call the excel exporter it goes through the series of events as normal. If we do call the excel exporter it will go through the page load event and unexpectedly go into the link button click event.