Hi guys,
I have been using the following code in order to export my pivot grid to an MS Excel file:
protected void ImageButtonExportExcel_Click(object sender, ImageClickEventArgs e)
{
var filename = ("Controlling_" + DateTime.Now.ToString());
//
ASPxPivotGridExporter1.ExportXlsToResponse(filename, true);
}
The code worked fine with v11.1 on my local development machine and on our productive server. Since I updated to v11.2 it is still working fine on my local machine, but the file returned from the production server is empty. It does not matter which format I'm exporting to (xls, xlsx, csv, etc.). The file is always 0 Bytes.
Does that make any sense to you?
Thanks
Ingmar
Bug Report
B209131
Visible to All Users
Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Hi Ingmar,
Thank you for your report. It appears that the information you provided does not allow us to clearly diagnose this issue.
If possible, please provide a small sample project to illustrate your ASPxPivotGrid initialization approach and fill in the Steps to Reproduce section of this ticket. We will check for a suitable solution.
Thanks,
Alex
Hello again,
I just replied to my other ticket http://www.devexpress.com/issue=B209130.
Unfortunately I don't have time to setup a demo project. As already mentioned in B209130, all I did was replacing the v11.1 DLLs with the corresponding v11.2 files. And of course I changed the references in the web.config.
Did you guys change anything about permissions? Maybe that's why exporting with v11.2 works fine on local machines, but not on production machines?
Thanks
Ingmar
Anyways: I just stepped back to v11.1 and everything works fine again. Are you guys really happy with your DLLs' naming convention? It's so much work to change all references and stuff, just because the file names differ from version to version. Well, I'm sure you had your reasons, but I would prefer all files to keep their file names - no matter which version/release.
Hi Ingmar,
Thank you for your response. We provide a special tool (Project Converter) to convert project files to a more recent version (see General Information > Upgrade Notes). In most situations, a manual assembly reference modification isn't necessary. Please process your project using the Project Converter tool and then re-deploy your application to the web server. In addition, check if all necessary assemblies are copied to the website Bin folder (see XtraPrinting > Product Information > Deployment). If this does not help, refer to the Event Viewer in the Control panel and check if there is any message related to the exporting procedure. I hope this makes the situation clearer.
Thanks,
Alex