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
generate the package so that you can reuse it when you rebuild the package.
This means you'll probably have to come up with some system of checking out the
source file, generating and updating the PackageCode and checking it back into
source control instead of relying on WiX to do this for you at build time.
This way when you pull the tree and build the package you can disable the
previous step and have an identical package.
But it's probably more practical to not do this. Rarely have I ever been
given a requirement to reproduct the exact same build. What they usually want
is to create a new branch off of all the files that were used in a given build,
make a change and create a new +1 build. In this case it makes perfect sense
to continue to allow WiX to dynamically generate the PackageCode at build time.
Kelly Leahy <[EMAIL PROTECTED]> wrote:
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 bad idea and that you
should save every MSI that you release somewhere 'special' rather than relying
on being able to rebuild them), you need to force all the "autogenerated" IDs
to be identical from one build to the next. The only way to do this is to
fully specify all those IDs (packagecode productcode upgradecode, etc.) and
then make sure you update them when appropriate (when building a "new" version
of the MSI).
Kelly
[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED] 11/26/2007 11:59 AM Please respond to
[EMAIL PROTECTED]
To
wix-users@lists.sourceforge.net cc
Subject
[WiX-users] Recreating duplicate .msi from revision control system
We are using WIX 2.xx tools for a project which is kept under revision control.
I'm trying to validate that I can reproduce an exact version of our software
including the MSI distributable for historical purposes. However, I find that
if I produce an MSI file twice using the same .WXS input files the resulting
MSI is slightly different.
At first I did not think it would be an issue, a binary diff shows only about
30 bytes are different and I expected it was a time stamp or some other trivial
detail. However, if I install with the first MSI, delete the MSI, recompile
the MSI, and run the same MSI it complains that the product of a different
version is already installed and must be removed from add/remove programs.
I know I could use vomus mode to override this, but if I run the same MSI I
installed with originally it automatically asks to uninstall which is the
behaviour I'm looking for.
Is it possible to reproduce the exact same MSI twice so long as all the inputs
are unmodified?
Thanks in advance,
Jason Riffel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
**************************************************************************************
This communication is intended solely for the addressee and is
confidential. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in
reliance on it, is prohibited and may be unlawful. Unless indicated
to the contrary: it does not constitute professional advice or
opinions upon which reliance may be made by the addressee or any
other party, and it should be considered to be a work in progress.
Unless stated otherwise, this communication does not form a prescribed
statement of actuarial opinion under American Academy of Actuaries
guidelines.
**************************************************************************************-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
---------------------------------
Be a better sports nut! Let your teams follow you with Yahoo Mobile. Try it now.-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
