See my post earlier this week
(http://n2.nabble.com/correct-upgrade-table-td4876031.html) showing
the solution I've come up with to prevent the user from installing
different 'builds' of the same product.
On Wed, Apr 14, 2010 at 6:13 PM, Viv Coco wrote:
> I got into this problem once when I did
s message and notify us immediately.
> Thank you for your cooperation.
> -Original Message-
> From: Viv Coco [mailto:vcotirl...@hotmail.com]
> Sent: Mittwoch, 14. April 2010 10:13
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Un
On 4/14/2010 9:26 AM, Johann Taferl, T-AU wrote:
> try using the "windows installer clean up" to delete the entry in your
> software list.
>
Avoid MsiZap at all costs: It modifies MSI's knowledge of what's
installed but doesn't actually remove any resources. Instead of mucking
around with t
I fix the uninstall problem.
I installed a ODBC driver using the functionality in wix and installed the
files into the System32 folder. I made the files permanent, but the odbc
driver funtionality in wix still wanted to remove the driver which failed.
After moving the driver files for odbc to
nk you for your cooperation.
-Original Message-
From: Viv Coco [mailto:vcotirl...@hotmail.com]
Sent: Mittwoch, 14. April 2010 10:13
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Uninstall problems
I got into this problem once when I did the following:
I got into this problem once when I did the following:
1) Create MyInstaller.msi Version X.X.X
2) Use this installer to install my product
3) Create again the MyInstaller.msi Version X.X.X, meaning a new rebuild
of the msi but with the same version and different Product GUID and
Package GUID as i
On 4/13/2010 9:04 AM, Jeffrey Bindinga wrote:
> Where should I be looking in this case?
>
Verbose log. It will show you what MSI decided to do with each feature
and component.
--
sig://boB
http://joyofsetup.com/
--
7 matches
Mail list logo
