Yeah, it's a little silly. The link I posted is the format on the VMX file. But internally in the uuid property does it differently. The number is the same. Unless you're using the VMX file at some point though, I would just use the uuid property from the SDK. Why the formats are different, who knows? You figure if you do have to use the VMX format at some point though, you could just parse the string out to w/e format you're looking to work with (guessing the sdk uuid property for FindByUuid calls).
To make it even more interesting, I think I once used WMI to compare the Windows BIOS UUID to the VMware UUID and the number wasn't even in order. I didn't spend much time on it though, was just curious one afternoon.
Heh, thats kind of what I figured. Can I at least rely on the dashes always being in the same spot?
I'm in an environment where memory matters, so I'd rather store it as a 128-bit number than a character array with a bunch of dashes (more than doubles the size).
Well, they are following the standard UUID format....so I hope so
"In its canonical form, a UUID consists of 32 hexadecimal digits, displayed in 5 groups separated by hyphens, in the form 8-4-4-4-12 for a total of 36 characters" is the official definition. I think it would be unlikely they intentionally change that format. You could just convert it to its 128bit form.
Sounds like you're working on one of the small footprint terminal client devices. Just saw a demo of one at my current assignment. Definitely getting slicker with the integration with VMware and Virtual Center.