Kelly is exactly correct. In this case, the first autogenerated GUID
that is getting you is the Package/@Id. The MSI SDK says that the
Package/@Id should be unique for every MSI file. Arguably you could say
the Ids should be the same in this case (and you could override the
autogenerate) but
Your rebuilt MSI is getting a distinct PackageCode. Normally it's a best
practice for each package to get a distinct PackageCode.
I suppose in your CM environment, if the goal is to really reproduce the
*EXACT* package, then you'll have to preserve the PackageCode that was used to
gen
I don't know if it's possible to produce exactly the same MSI, but I think
your problem is related to automatically generated package codes or
product codes. If you want to be able to rebuild an MSI that acts exactly
the same as one that already went out the door (I think this is generally
a b
3 matches
Mail list logo