: [WiX-users] Upgrade nightmare again
I have the following immediate custom actions sequenced during upgrade
ExportRegistry - to export a specific hive on windows registry as .reg file
ModifyRegistry - to make a few modifications for the new product
ImportRegistry - to import the .reg file
and
I have the following immediate custom actions sequenced during upgrade
ExportRegistry - to export a specific hive on windows registry as .reg file
ModifyRegistry - to make a few modifications for the new product
ImportRegistry - to import the .reg file
and the CAs are scheduled as
ExportRegist
bject: Re: [WiX-users] upgrade nightmare
You should change the ProductCode as well.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Some
> user
> Sent: 30 March 2007 07:40 AM
> To: wix-users@lists.sourceforge.net
> Subjec
You should change the ProductCode as well.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Some user
> Sent: 30 March 2007 07:40 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] upgrade nightmare
>
the problem is that requiring commandline parameters or bootstrapper is
unacceptable for us, we have seen that our users are too stupid to type a
commandline (!?)
so I have been told toto make a thing that can do installs and updates on
the same package without requiring any commandline parameter
Alexander Gnauck wrote:
> Requirements:
> - Install and Updates must be redistributable with group policies.
> - The updates/patches must run without having the original MSI.
> - The latest update must be always be able to update the product,
> doesn't matter which previous version is installed.
>
Hello,
I am fighting for some days now with figuring out the best update
strategy and writing samples for updating and/or patching.
Is read the tutorial (http://www.tramontana.co.hu/wix/lesson4.php)
several times but there are still lots of open questions. Also the MSDN
doesn't help that much w
7 matches
Mail list logo
