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

Free Support Forum - aspose.com

Aspose.Cells throws Exception on 64 bit machine

v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);}


I am using Aspose.Cells

I have tried to run my application in 64 bit Machine which generates Excel and it throws an Exception as

{System.BadImageFormatException: is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)

And I have downloaded the Latest version of Aspose.Cells and ran the Application ,same Exception is thrown.

Is there any latest version of Aspose.Cells

Please help me to solve this problem.



This message was posted using Email2Forum by nausherwan.aslam. (attachment)


Thank you for considering Aspose.

Well, if you have installed Aspose.Cells for .NET component using Aspose.Cells.msi installer, there will be two dlls on the installation path. You may use the dll in the NET2.0 folder for 64 bit machine. Please see the following documentation link for your reference.


You may also check the following links which may help you regarding use of DLL and referring them in your project.



Also, I have attached the latest DLL which can be used with 64 bit machine. If you need any further assistance, please do let us know. We will be happy to help you out.

Thank You & Best Regards,

Hello Aslam, I am using latest version of Aspose.cells. with VS2010 + Windows server 2008, which you are attached in the forum. Application throwing following exception .

System.BadImageFormatException: Could not load file or assembly 'aspose.cells.dll' or one of its dependencies. is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)

can you please help me out what i am missing out here


Please download and install Aspose.Cells for .NET v5.0.0: http://www.aspose.com/community/files/51/.net-components/aspose.cells-for-.net/entry243604.aspx , we do provide Net framework client profile version specifically for VS.NET 2010, see the document for reference:

Kindly let us know if you still find any issue.

Thank you.