Thank you for clarifying this for me, Peter!
I ran the MSI without REINSTALL and REINSTALLMODE and it worked like a charm!
Your explanation was perfect and Rob's response provided further
clarifications on this page
http://stackoverflow.com/questions/526707/major-vs-minor-upgrade-in-windows-instal
ximum="$(var.ProductVersion)" IncludeMaximum="no"
>> Property="OLDERVERSION_BEINGUPGRADED"
>> MigrateFeatures="yes" />
>>
>>
>> As far as App Compat, I was talking in the logs.
>>
>>
versions of the old and
> new MSI?
>
> -Original Message-
> From: Alec Swan [mailto:alecs...@gmail.com]
> Sent: Wednesday, September 19, 2012 2:49 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] UI upgrade succeeds, but silent u
Hello,
We are testing upgrade from an older version to the version we are
about to release. We noticed that upgrading "msiexec.exe /i my.msi"
successfully upgrades the old product files with the new ones.
However, silently installing with the following command fails:
msiexec.exe /i my.msi REINSTAL
before ?
>
> -Original Message-----
> From: Alec Swan [mailto:alecs...@gmail.com]
> Sent: 23 August 2012 16:34
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] UnistallString is not written in
> Software\Microsoft\Windows\CurrentVers
, Aug 23, 2012 at 9:33 AM, Alec Swan wrote:
> Actually, I just found that
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5D6E0940-C1EB-4C60-8A36-54D6BCCF5C02}
> contains an UninstallString for our product. Now I have to track down
> how we ended up with a GUID
.
I am new to all this and appreciate any help with this.
Thanks,
Alec
On Thu, Aug 23, 2012 at 9:27 AM, Alec Swan wrote:
> We can still uninstall the product from Add/Remove Programs but there
> is no entry for our product under
> HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curre
t ARPNOREMOVE ? That would suppress the uninstall string.
>
> -----Original Message-
> From: Alec Swan [mailto:alecs...@gmail.com]
> Sent: 23 August 2012 15:22
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] UnistallString is not written in
ller itself writes the value.
> http://msdn.microsoft.com/en-us/library/aa372105%28v=VS.85%29.aspx
> However, the uninstall string is not used by Windows Installer so does it
> matter that it wasn't written ?
>
> -----Original Message-
> From: Alec Swan [mailto:alecs..
Hello,
I am trying to track down why our installer generated using Wix 3.0
stopped writing the UninstallString value in
Software\Microsoft\Windows\CurrentVersion\Uninstall\ registry key. At
some point we must have changed some code that broke this behavior.
Where should I start troubleshooting th
Does anybody have sample code or pointers on how to pass parameters or
arguments to MsiProductInstall() in bootstrapper?
On Fri, Mar 16, 2012 at 10:55 AM, Alec Swan wrote:
> session.Log seems to work fine, thanks. However, I can only see these
> messages in the log file if I pass /l*v par
is (Jscript example)
>
>
>
>
> The call from my first custom action looks like this
>
> Session.Property("WriteToMSILog") = "Process Name: " + pProps[proc];
> Session.DoAction("WriteToMSILog");
>
> -Original Message-
> From:
ows/desktop/aa372847.aspx for information on Windows
>> Installer Logging. In particular check the Normal Logging section at
>> http://msdn.microsoft.com/en-us/library/windows/desktop/aa370536.aspx
>> for an explanation of your options.
>>
>> Edwin G. Castro
>
overwritten. If you set it with a type 51 it just gets ignored.
>
> Phil W
>
> -Original Message-
> From: Alec Swan [mailto:alecs...@gmail.com]
> Sent: Thursday, March 15, 2012 10:09 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [Wi
g it causes a fair number of install
>> failures, particular in install/repair/uninstall cycles.
>>
>> --
>> John Merryweather Cooper
>> Build & Install Engineer - ESA
>> Jack Henry & Associates, Inc.®
>> Shawnee Mission, KS 66227
>> Office: 913-341-
WiX-users] Setting MsiLogFileLocation property
>
>
> I don't think you can set the log file using MsiLogFileLocation. I think
> it
>
> *gets* set to the log file location. You can force your package to require
>
> MSI 4.0 by setting the Package/InstallerVersion attribute.
&g
Hello,
I need to enable verbose logging and configure MSI log file location.
I am currently doing this by adding the following properties inside of
my .wxs file:
1
x:/WIX/wix-msi.log
...
Is this the right place for these properties?
If so, then I am assuming that the reason why they are
17 matches
Mail list logo
