Hi all, I have a foo.msi in my temp folder when I install my foo application, with feature A. Then I go to the Add-Remove Program control panel, click Change, and want to install a new feature B of foo application. I got two problems then: 1, the UAC does not popup, when I click Change button and start to install feature B. This will cause some custom actions fail because it does not have enough privilege. 2, A message dialog pop up ask: The feature you are trying to use is on a network resource that is unavailable. Click OK to try again, or enter an alternate path to a folder containing the installation package "foo.msi" in the box below: ... I've already deleted my foo.msi in temp folder, so I point to c:\windows\installer\245bfd.msi (the copy MSI created during installation), but the dialog still shows.
I tried rename the 245bfd.msi to foo.msi, and the UAC pops up, the change success. So the question: why installer requires the MSI with exactly the same name? Seems change is really a common scenario, and most time customer will not have the msi file by hand, but let windows installer use the cached one. How does this work? Am I doing anything wrong, that breaks this scenario? Thanks, -Elfe ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
