Hi,
My msp patch is missing Version and Publisher info in Installed Updates
window in ARP for 64 bit machines. I've populated all the fields in PCP
correctly but still it doesn't show up. It works fine on 32 bit machines.
My MSI is a 32 bit MSI so that might be one reason why it fails for 64 bit
Thanks Namrata,
I am just wondering if we can change the Registry path from HKCU to HKLM
while creating shortcut of application.
ComponentGroup Id=TestWindowServiceShortcut
Directory=ApplicationProgramsFolder
Component Id=TestWindowServiceShortcut
Guid=01E98283-4246-46BC-A39F-0F1975C95AA6
Hi,
Thats exactly what I was looking for thanks so much for your help.
George.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Search-for-IIS-Modules-tp7600726p7600748.html
Sent from the wix-users mailing list archive at Nabble.com.
There is not quite enough log to be sure, but the other possibility is
that the cached MSI (typically in C:\Windows\installer) is missing,
and that will result in a search for the original MSI source. Also not
clear from the log is if this is the result of an explicit
ResolveSource action or
I have a machine where I cannot upgrade my old product to the new version.
It is just on this one machine - it has successfully upgraded on many other
machines of the same version of windows.
Thanks in advance if anyone can tell me why this happens (it is intermittent
even on the same
It appears the old MSI requires it's source (that's a big no-no on uninstall).
Can you successfully uninstall it directly (i.e. not via an upgrade)?
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
On the MsiPackage element, you must set EnableFeatureSelection=yes (
http://wixtoolset.org/documentation/manual/v3/xsd/wix/msipackage.html) to
get feature information in BootstrapperApplicationData.xml.
On Tue, Jun 30, 2015 at 11:04 AM, Brian C Cooke tonic...@gmail.com wrote:
How can I provide
How can I provide functionality for feature-level selection in my custom
bootstrapper created by burn? This link (
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-create-a-feature-tree-with-burn-td7579948.html)
seems to suggest I can do so by examining the
Here's the whole log, attached. And a log from when it worked - on the same
machine!Thanks for looking!
On Tuesday, June 30, 2015 2:16 PM, Phil Wilson phildgwil...@gmail.com
wrote:
There is not quite enough log to be sure, but the other possibility is
that the cached MSI (typically
9 matches
Mail list logo