I'd look at divorcing the assembly version information from the file version
information. Use the AssemblyFileVersion property to set the file's version.
If you're installing to the GAC then you need to use the -fv switch with
light to ensure that the new file overwrites the old file in the GAC.
You can always specify your COM GUIDs in the application source code. It's
my belief that the .NET Framework does not actually care what the GUIDs are,
as long as they are registered correctly - it only uses the GUIDs to locate
the correct class or interface to load. However, you should be consistent
in, for example, generating your type library (if any) and registration
information.
By default .NET generates its GUIDs based on a hash of the type name, using
the full type name including the assembly name and version number. You can
use a ComCompatibleVersionAttribute at the assembly level to force a
particular version number to be used to compute the GUIDs.
--
Mike Dimmick
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sean Li (XIN)
Sent: 10 August 2007 01:24
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Auto-incremented versions
Hi,
What's the best way to handle information that changes in every build? For
example, the assembly version of my COM registration is different every
build because we auto-increment the minor version number. Is there any best
practice to handle this kind of information?
Thanks a lot,
Sean
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
