GUID
From Just Solve the File Format Problem
(Difference between revisions)
(Removed from deprecated "Binary Data" category) |
|||
| Line 11: | Line 11: | ||
In binary form, the first three fields are supposed to be stored using native [[endianness]]. Since Microsoft platforms usually use little-endian byte order, the above GUID would typically be stored as the following 16 bytes: | In binary form, the first three fields are supposed to be stored using native [[endianness]]. Since Microsoft platforms usually use little-endian byte order, the above GUID would typically be stored as the following 16 bytes: | ||
03 02 01 00 05 04 07 06 08 09 0a 0b 0c 0d 0e 0f | 03 02 01 00 05 04 07 06 08 09 0a 0b 0c 0d 0e 0f | ||
| + | |||
| + | == See also == | ||
| + | * [[CLSID]] | ||
| + | * [[UUID]] | ||
== Links == | == Links == | ||
Latest revision as of 15:56, 2 October 2017
A GUID (globally unique identifier) is an arbitrary 128-bit identifier. It is the Microsoft version of UUID.
[edit] Format details
When written in standard text form, a GUID looks something like this:
{00010203-0405-0607-0809-0a0b0c0d0e0f}
In binary form, the first three fields are supposed to be stored using native endianness. Since Microsoft platforms usually use little-endian byte order, the above GUID would typically be stored as the following 16 bytes:
03 02 01 00 05 04 07 06 08 09 0a 0b 0c 0d 0e 0f
