I have a msp patch and msi minor pgrade processing result where a specific <app>.config file setting which has underwent some miner content changes in the v1.1 release is not getting updated.
If I diff my v1.0 target adminInstall and my v1.1 update adminInstall used to by the old msimsp patch method for msp generation I can see the expected differences between the two releases of the particular file in question. When I run a v1.1 clean install I get the expected file contents. The file in question gets updated during v1.0 deployment by associated component <util:XmlFile settings that update wcf endpoint address settings to be deployment environment specific. Is it those updates to that are preventing the v1.0 to v1.1 msp patch minor upgrade and msi minor upgrade processes from updating that file to contain the just the v1.1 added content? If so is there syntax to instruct v1.0 to v1.1 msp patch and msi minor upgrade processing to replace that file regardless and rerun the <util:XmlFile settings component step? ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
