We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Updating version. Save method changed

Aspose.Cells Product Family
#1

I am currently working on a project that is upgrading all of our use of Aspose.Cells to the newest version. [4.1.2.0 to 5.1.3.0]

I am running into a problem with the updated Aspose.Cells.Workbook.Save method. The interface has completely changed.

Can you recommend how I would rewrite this line of code using the 5.1.3 interface?

XLS.Save(OutputFileName, Aspose.Cells.SaveType.OpenInExcel, Aspose.Cells.FileFormatType.Default, System.Web.HttpContext.Current.Response);

#2

Hi Scott,

In Updated version of Aspose.Cells, save method will be as follows:

workbook.Save(HttpResponse, sFileSavePath, ContentDisposition.Inline, new SaveOptions());

For more information, please follow the link below:
http://www.aspose.com/documentation/.net-components/aspose.cells-for-.net/aspose.cells.workbook.save_overload_18.html

Thanks,

#3

I do not have that option in my version (5.1.3.0).

I only have the following Save methods:

void Workbook.Save(string fileName)

void Workbook.Save(Stream stream, Aspose.Cells.SaveFormat saveFormat)

void Workbook.Save(Stream stream, Aspose.Cells.SaveOptions saveOptions)

void Workbook.Save(string fileName, Aspose.Cells.SaveFormat saveFormat)

void Workbook.Save(string fileName, Aspose.Cells.SaveOptions saveOptions)

#4

The biggest problem is that new versions of the component is not backwards compatible. I don't see why this would be necessary...

#5

Hi,

The new versions are backward compatible. If you are building a web application, please use the Aspose.Cells.dll in the net2.0 directory.

For your information, the dll in net3.5_ClientProfile directory is used only for the console application with Net frame client profile. Please check your project, it is possible that your project is referencing this dll. For complete reference, please read the readme.txt file in the bin directory.

Thank you.

#6

So there are multiple versions of code with the same assembly name and version number?

I'm glad your deployment strategy is straight forward.

#7

Hi,

Well, we actually target all the platforms(including Microsoft Windows or Mono platforms), we provide Aspose.Cells.dll version compiled on different .NET frameworks (e.g 1.x, 2.0, 3.5 (client profiles) or 4.x etc.) for both 32-bit and 64bits. All you need you do is to select the appropriate Aspose.Cells.dll version from different folders e.g net1.x, net2.0 etc. see the topics for reference:
http://www.aspose.com/documentation/.net-components/aspose.cells-for-.net/referencing-aspose-cells-component-from-a-net-project.html
http://www.aspose.com/documentation/.net-components/aspose.cells-for-.net/using-aspose-cells-component-on-32bit-and-64bit-platforms.html

Thank you.