I know of no scenario where you'd want to do that. That's on reason why it
isn't made easy. <smile/>

On Fri, Apr 30, 2010 at 9:12 AM, Castro, Edwin G. (Hillsboro) <
edwin.cas...@fiserv.com> wrote:

> If you absolutely need to change the Product UpgradeCode on every build (Is
> this a good idea?), then you'll need to extend your build process to do it
> yourself. XML is relatively easy to change, especially in PowerShell.
> Executing something like the following could help:
>
> powershell -command "$wixFile = 'Product.wxs' ; $doc = [xml](Get-Content
> -Path $wixFile) ; $doc.Wix.Product.UpgradeCode =
> [System.Guid]::NewGuid().ToString() ; $doc.Save($wixFile)"
>
> Edwin G. Castro
> Software Developer - Staff
> Electronic Banking Services
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291
> www.fiserv.com
> Please consider the environment before printing this e-mail
>
>
> > -----Original Message-----
> > From: Pally Sandher [mailto:pally.sand...@iesve.com]
> > Sent: Friday, April 30, 2010 8:14 AM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Candle: Add new GUIDs to user specified
> > locations atcompile time?
> >
> > <Product Id="*" />
> > <Component Guid="*" />
> >
> > Good luck with changing the UpgradeCode every time you build. You may
> > as
> > well just remove it instead as it's about as useful as a chocolate
> > fireguard with that requirement.
> >
> > Palbinder Sandher
> > Software Deployment & IT Administrator
> > T: +44 (0) 141 945 8500
> > F: +44 (0) 141 945 8501
> >
> > http://www.iesve.com
> > **Design, Simulate + Innovate with the <Virtual Environment>**
> > Integrated Environmental Solutions Limited. Registered in Scotland No.
> > SC151456
> > Registered Office - Helix Building, West Of Scotland Science Park,
> > Glasgow G20 0SP
> > Email Disclaimer
> >
> > -----Original Message-----
> > From: jeff00seattle [mailto:jeff_tan...@earthlink.net]
> > Sent: 30 April 2010 16:02
> > To: wix-users@lists.sourceforge.net
> > Subject: [WiX-users] Candle: Add new GUIDs to user specified locations
> > atcompile time?
> >
> >
> > Hi
> >
> > Is there a way that a new GUID can be added to specific location within
> > WiX at compile time?
> >
> > I have created a common WiX file, and I want to add a new GUID upon
> > each
> > run
> > to:
> > * Product Id
> > * Product UpgradeCode
> > * Component Guid
> >
> > I read in one blob
> > http://johnmcfadyen.spaces.live.com/?_c11_BlogPart_BlogPart=blogview&_c
> > =
> > BlogPart&partqs=cat%3DWiX
> > John McFadyens Windows Installer Blog  that using
> > "????????-????-????-????-????????????" creates a new generated GUID
> > each
> > time the compiler runs. This ensures you are running with the rule of
> > creating a new package code for each iteration of your package.
> >
> > However, this did not work.
> >
> >
> > -----
> > Thanks
> > Jeff in Seattle
> > --
> > View this message in context:
> > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Candle-
> > Add
> > -new-GUIDs-to-user-specified-locations-at-compile-time-
> > tp4986130p4986130
> > .html
> > Sent from the wix-users mailing list archive at Nabble.com.
>
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to