I just upgraded to Asposes 3.5.3. I am noticing that code that worked under Aspose version 3.0 no longer works. Previously, I was using Aspose.Excel.DocumentProperties to set the "Author" property. It worked. Now, using Asposes 3.5.3 that API does not appear to be supported, so I switched to using Aspse.Excel.BuiltInProperties, which seemed the new correct way to get at the "Author" property. The code compiles and runs, but the Author property is not changed in the output file. (The debugger thinks that the value is set, though.)
Could you please double-check this functionality and let me know what you think is happening? Thanks.
We ported code to read document properties from windows API interop to full managed code. This problem may be caused by the porting. We will check and fix this issue ASAP.
I am seeing odd behavior with the DLL patch. For all but one run of the exact same code, I get a NullReferenceException in Aspose.dll. Everything looks correct in the debugger (I see an Author string with all ASCII characters). I am passing valid values to Aspose.Excel.Save, code that has been working for a long time:
[NullReferenceException: Object reference not set to an instance of an object.]
at Aspose.Excel.RW.?.?(BuiltInDocumentProperties ?, CustomDocumentProperties ?, ? ?)\r\n at Aspose.Excel.Worksheets.?(FileFormatType ?)\r\n at Aspose.Excel.Worksheets.?(String ?, SaveType ?, FileFormatType ?, HttpResponse ?)\r\n at Aspose.Excel.Excel.Save(String fileName, SaveType saveType, FileFormatType fileFormatType, HttpResponse response)\r\n
P.S. - I just noticed that when using version 3.5.3.0 (NOT the patch that gives the NullReferenceException), if I hover my mouse cursor over an Excel file that I generated, the Author property is shown. BUT the Author property appears blank if I open the Excel file and use File | Properties.
In previous v3.5.3, we have also found the Author property shows correctly in windows explorer but doesn't show correctly in MS Excel. This bug is fixed.
For this NullException issue, I think it may relate to your template file.
I have attached a simple Unit Test that demonstrates the problem. If your environment does not support the Microsoft.VisualStudio.TestTools.UnitTesting namespace, just copy the 6 lines of code into your test bed and see the results.
// Results Summary:
// version 3.5.3.0 - Assertion fails. does not equal <>.
// version 3.5.3.1 - System.NullReferenceException: Object reference not set to an instance of an object.
Fixed! I’m not sure when the release bumped to 3.5.3.2. (I was testing with 3.5.3.1 – up from 3.5.3.0). In any case, the problem is resolved. Thank you.