Greetings,
Aspose.Cells - 4.8.2
I've got a client that is reporting a problem with our applicatioin, howver, looking at the stack trace (which I point to a diagnostic screen) I see that it is Aspose that has thrown an exception. Since the assembly is obfuscated, I cannot tell exeactly where or why the Aspose component has failed. A copy has been attached
When you look at the stack trace, you can see my application calling my export function, then calling a check format function, then calling the Aspose.save function, then a bunch of obfuscated Aspose calls related to the save function (at least what I think they are) and then finally the failure when your save function calls the system.array.copy function.
When the aspose save function calls the system.array.copy function, the specific failure message is "Destination array is not long enough. Check destindex and length, and the array's lower bound"
Now, of course, I cannot get the application to reproduce the problem in development, but I need to figure out why and where this is happening.
I've attached the file that she reports that this is happening to when it is saved. What is strange is that our "checkformat" function, which is what calls your save function is simply opening the file and checking the worksheets to make sure that the right worksheets are there, and then saving the file (actual code attached).
Of course, after the error is thrown, the file is reduced to 0 in size, which ruins the original file.
These guys are breathing down my neck, your assistance is appreciated.
<?xml:namespace prefix = v ns = "urn:schemas-microsoft-com:vml" /> <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />