product code generation
I have been packaging long enough that I am should know the answer to this question, but this is the first time I have run into an issue.
The question: When repackaging (in this case, with WPS), what is used to generate the .msi's product code? Is it randomly generated, or is some algorythym run against some piece of information from the souce software?
Craig --<>.
The question: When repackaging (in this case, with WPS), what is used to generate the .msi's product code? Is it randomly generated, or is some algorythym run against some piece of information from the souce software?
Craig --<>.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
bkelly
19 years ago
It is a published algorythm. There is a tool in the SDK called uuidgen.exe, which is located in the "C:\Program Files\Microsoft SDK\Bin" directory, that can do it for you. Or even better, the below VBS will do the trick...
Set TL = CreateObject("Scriptlet.TypeLib")
GUID = TL.Guid
WScript.Echo GUID
Posted by:
craig16229
19 years ago
Okay, that gives me half the knowledge I need. Let me explain why I ask:
I am repackaging Studio MX for a new client. I elected to break the components up into their own packages. Each is ending up with the same product code. So, what does the alogorythm run against to get created?
Craig --<>.
I am repackaging Studio MX for a new client. I elected to break the components up into their own packages. Each is ending up with the same product code. So, what does the alogorythm run against to get created?
Craig --<>.
Posted by:
bkelly
19 years ago
It uses the time and a few other things to generate what should be a "globably" unique number, so if you are trying to dynamicaly recreate your component GUIDs somehow, I think you're out of luck. There is a bit more info on how Microsoft does GUIDs here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetcomp/html/PPCGuidGen.asp
Hope this helps,
Bob
Hope this helps,
Bob
Posted by:
craig16229
19 years ago
Bob,
Thanks for that information. It was exactly what I needed to know, and has kept me from going down the wrong troubleshooting path.
Based on what you provided, it seemed very unlikely - if not impossible - to have matching codes on different packages. After reviewing those codes again, I found they are not the same. Something else is causing my issue; it's back to the drawing board.
Craig --<>.
Thanks for that information. It was exactly what I needed to know, and has kept me from going down the wrong troubleshooting path.
Based on what you provided, it seemed very unlikely - if not impossible - to have matching codes on different packages. After reviewing those codes again, I found they are not the same. Something else is causing my issue; it's back to the drawing board.
Craig --<>.
Posted by:
bkelly
19 years ago
No problem! If you are trying to match up component GUIDs between packages (presumably for an upgrade MSI) - Wise Package Studio's UpgradeSync utility may be what you are looking for, as this is one of its functions.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.