Closed koyuyesil closed 9 months ago
Hi @koyuyesil , I'm not sure to have fully understood but I think you want to use OpenMcdf to create a specific editor for you use case (let me know if I'm correct). If so you should use OpenMcdf as a dependency/base library in your project because I can't include an editor extension that is too much bound to a specific use case for a general usage library. You should start from the Structured Storage Explorer as template and specialize it for your needs, for example. Please, let me know If I've correctly understood your point or if I've totally missed it and you need help for something different.
Best Regards, Federico
As a base library, it already works very well. Is it possible to make the library more flexible for applications that use the base library but have their own custom data structures? For example, if we program a Structures.DLL and convert the data fragment into this object, how would it work? Like this code snippet:
var str = cf.RootStorage.GetStream("NV_ITEM_ARRAY");
var co = str.AsOLEPropertiesContainer();
But something like AsOleNvItemArray()
.
@koyuyesil I think you could implement an extension/wrapper class that uses the same logic of the aforementioned example just as
public static NvItemArray AsOleNvItemArray(this CFStream cfStream)
{
return new NvItemArray(cfStream);
}
Do you see any specific issue with this approach in your Use Case?
Qualcomm uses the MCDF structure for NV Items backup files. I'm familiar with the structure of these streams. How can I contribute to this branch? QCNWiew official app for wiewing i want make editor.
File Version;
FeatureMask (Bit Definitons);
Mobile_Property_Info summary;
Nv Numbered Items