Re: (De)-Serializing from/to VB (generic bytes)

Its too generic, see My.Computer.FileSystem.WriteAllBytes Method, its generic open :raw/binmode/print/close, bytes can be anything -- basically you need to get more specific, name of program, version.... docs

But you can always see what "file" and exiftool know about it ... there are OTHERS like Synalyze It! which support various formats

Comment on Re: (De)-Serializing from/to VB (generic bytes)

Replies are listed 'Best First'.
Re^2: (De)-Serializing from/to VB (generic bytes) by belg4mit (Prior) on Jan 18, 2016 at 22:25 UTC
Aye, see Re^2: (De)-Serializing from/to VB. I already know what type of file it is … a Jet database. But for some unknowable reason, rather than inserting features of an object as records in another table, features of an object are stored as a serialized BLOB in the object table. `-- In Bob We Trust, All Others Bring Data.`	[reply]
Re^3: (De)-Serializing from/to VB (generic bytes) by soonix (Canon) on Jan 19, 2016 at 12:25 UTC
If it's really a Jet database and you're on Windows, you might prefer to access it via DBI and DBD::ADO or ODBC? Don't know how to do this from Linux or other, however...	[reply]
Re^4: (De)-Serializing from/to VB (generic bytes) by Anonymous Monk on Jan 20, 2016 at 14:59 UTC
I have, that was how I discovered that they're storing serialized, record-based data in a database :-P	[reply]
Re^3: (De)-Serializing from/to VB (generic bytes) by hotchiwawa (Scribe) on Jan 19, 2016 at 10:20 UTC
Maybe I'm wrong but if you know the encoding and let's say that the data are not crypted, normally when translating the bytes in characters you should get the text serialized with the tags... if the structure is fixed, it will be easy but if tags are removed from time to time (optional fields), this could be more difficult to get the full structure.	[reply]


"be consistent"
	PerlMonks