- You have talked about missing storages and streams in the OLE package. We are not able to observe this OLE package anywhere. Please let us know if this OLE package can be seen in Excel or not. Please provide us detail about viewing this OLE package structure in template file and output file.
OLE package is not inside sample file. File it self is OLE package (or compound file see Compound File Binary File Format. OOXML files are ZIP archives. Legacy and encrypted OOXML formats are compound files (OLE structured storage). Developers will now what I am talking about.
Being a compound file, sample file has storages and streams that are sown on the screenshot from my initial post. I get storage structure visualization using API that works with compound files. You can use something like OpenMCDF. After resaving sample file, it loses ’ DataSpaces’ storage.
So I asked to explain why ’ DataSpaces ’ storage is removed?
- Regarding the GUID issue, please provide us details what to observe in registry before running the program and what to observe after running the program. Also please share with images and more details that what should be the actual behavior in the registry and steps to observe that behavior using Excel only.
- Regarding setting Application GUID for encrypted XLSX file, you mentioned that this issue was not there earlier. Please share the Aspose.Cells version where it was working fine earlier and steps to observe this difference using that old version without this issue and the newer version having this issue. We need to know whether this issue of change in application GUID is faced with encrypted files only or it is there for normal files (unencrypted) as well.
Sorry, seems it is my mistake. Aspose.Cells was always (or at least for very long time) inserting non-Zero Appplication GUID, and removing ’ DataSpaces’ storage while resaving encrypted XLSX, XLSM…
About the Windows Registry: It does not matter when to open Windows Registry. I used it to show that Application GUID that is inserted by Aspose.Cells for encrypted OOXML formats is registered for XLS format.
GUID for .XLSX is {00020830-0000-0000-C000-000000000046}, for XLSM is {00020833-0000-0000-C000-000000000046}. I have taken it from the Registry too.
MS Word/Excel/PowerPoint always puts Zero Application GUID for encrypted OOXML formats. If you resave sample file by Aspose.Celss, then resave by MS Excel, then MS Excel replaces GUID inserted by Aspose.Cells to Zero GUID.
Expected behavior for Application GUIDs: I do not know what expected behavior is, because I cannot find written confirmation in MS documentation. I just shared my finding with you that MS applications set Zero GUIDs for encrypted OOXML files.