-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unrecognized property type #32
Comments
…nd SummaryInfo in .AsOLEProperties extension method. Structured Storage Explorer has default OLE_PROPERTY flag on. (Beta feature). Some ole property is not supported yet.
I've added some enhancement in OLE Properties handling that hopefully should allow DocumentSummaryInfo and SummaryInfo sets parsing. Please, consider OLE properties still in a beta stage because not all property types are supported and this feature needs a deep unit testing to be considered really a production-ready feature nevertheless it's a useful extension so please let me know if there are other issues possibly attaching an example file to analyze. |
Extension NuGet package 2.2.1.3 published. |
I just wanted to say thank you for sharing your work with us all.
My usage is a little indexing program at my work that monitors our Solid
Edge (CAD) files and and stores file links in an SQL table for fast
searching. Your code allows the indexing service to search model data
files for links without needing to have the CAD software installed on the
server. I'm excited to try out this improvement as these files have the
document properties you mentioned and sounds like this would help the
process of indexing those also.
Ben Nemec
…On Wed, Nov 21, 2018, 16:46 Federico Blaseotto ***@***.*** wrote:
I've added some enhancement in OLE Properties handling that hopefully
should allow DocumentSummaryInfo and SummaryInfo sets parsing. Please,
consider OLE properties still in a *beta* stage because not all property
types are supported and this feature needs a deep unit testing to be
considered really a production-ready feature nevertheless it's a useful
extension so please let me know if there are other issues possibly
attaching an example file to analyze.
Best Regards,
Federico
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AX_v9v6jEMevOG6mVAaY-HTLRHaOly1Nks5uxdfRgaJpZM4Ydh4O>
.
|
Thank you so much Federico, I'll go and get the new package now and test :) Much appreciated! |
Hi Federico, Unfortunately, this did not fix our issue. I have attached a .ppt file (in a zip) that contains a date, but cannot seemingly be grabbed by OpenMCDF. Some properties seem to have changed in this new version: "PropertyValue" is now "Value", for example. For some reason, I am now getting this error message.
I'll "Repair" my Visual Studio. |
Thank you for this test-case. I've found the issue (missing clipboarddata property type) and it will be fixed as soon as possible. |
Hi Federico, Thanks for looking at it again. I appreciate your efforts very much. |
… a PARTIAL commit: it should work for common case, OLE properties ---->read only<----. User defined properties not supported yet, Array properties not supported.
Please, take a look at current codebase (no nuget yet) to see if this partial commit fix reported issue. |
Hi, I can attach a sample file if that would be useful? Thanks. |
Hi, |
This file has Author and Keywords properties of type LPWSTR. |
LPWSTR support added. |
Please, take in account that OLEProperties Container still does not support write methods (NotImpementedException to avoid issues) |
@Numpsy please, let me know if current code base close this issue. |
Thanks @Numpsy. Yes, ole strings have null termination AND a size field so I think that it's better if client application applies a post filter to handle them in its preferred way at the moment. I will introduce some type of configuration parameter to specify how handle null characters. |
Seems like this is a thread hijack to me! Can I ask why this bug report has been closed? |
Sorry, but i thought that last report means "ok". If you think it's not i
will reopen.
Il giorno ven 7 dic 2018, 15:39 nullldata <notifications@github.com> ha
scritto:
… Seems like this is a thread hijack to me!
Can I ask why this bug report has been closed?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ARhAuDsFdGW-PT10B6JLT4Y1Vo2-u9zZks5u2n2zgaJpZM4Ydh4O>
.
|
We are currently trying to compile from source, however it's not yet compiling. Looking into it. From our perspective, we don't have a working solution currently. Will update when we successfully compile and test. Sorry for slow reply, I've been away. |
WooooHoooo! It works! :) Fede, you are a hero! :) Please let us know if this gets made into a nuget package, as I fear that using our compiled DLLs may not be updateable. |
@nullldata , i'm going to close issue. |
@ironfede Sure, no problem. Thanks again! :) |
Hi Ironfede,
We have been using your library in a project at work where I am grabbing the "Creation Date" property from old format office files that contain it (doc, xls, ppt, for example - pub and vsd files don't seem to have the property).
We found that it works really well, but some files throw an "Unrecognized property type" exception.
We can't figure out why.
When we check the files with "SSView", we can see the date exists.
Similarly, the date exists within the Windows File Explorer properties.
Our test code is simple:
The issue is thrown on the following line:
PropertySetStream ps = CFStreamExtension.AsOLEProperties(stream);
We can't figure out whether the issue is with the file, our code, or the library...
In 1 case, a file that was not working suddenly started working after we changed some document properties (removed author). Weird.
Attempting to do this on another file had no effect.
Attempting to find the original age of a document will help us with our document retention automation in SharePoint. This isn't our SharePoint code, it's just a console app to test pulling back the values from the stream.
With GDPR being a thing nowadays, handling all these old files is suddenly also a thing too.
Can you help please?
Thanks for your excellent work!
The text was updated successfully, but these errors were encountered: