wix3

问题 When products A and B each install several MSIs and some of the MSIs are the same, will uninstalling either A or B affect the other? Does install location matter? Also, what happens when common MSI C\'s version is higher in Product B and B upgrades C on install? Now uninstalling B will remove the common MSI C which breaks Product A. How do you handle this gracefully without using the Permanent flag? 回答1: The first thing that comes to mind with this question is whether the products in question

问题 I would like to use the WixUI_Minimal installer, but I don\'t want the license page. How can I do this? 回答1: I would simply use one of the already created WiX UI and override the sequence (make it higher so that it will override the previous setting): <Product> ... <UI> <UIRef Id="WixUI_InstallDir" /> <!-- Skip license dialog --> <Publish Dialog="WelcomeDlg" Control="Next" Event="NewDialog" Value="InstallDirDlg" Order="2">1</Publish> <Publish Dialog="InstallDirDlg" Control="Back" Event=

问题 WiX files always seem to include this line: <Directory Id=\"TARGETDIR\" Name=\"SourceDir\"> What is \"SourceDir\"? What is it used for? It\'s not a real directory name. Is it some kind of magical value? 回答1: From: http://robmensching.com/blog/posts/2010/1/26/StackOverflow-what-does-NameSourceDir-refer-to Honestly, it's something that we should have hidden from the developer but didn't. Sorry. The truth of the matter is that the Windows Installer expects the Directory tree to always be rooted

问题 Should I wrap all the files I want to install in individual components? What is the advantage of putting several files in one component? 回答1: One reason for "one file per component" is resiliency. When an application is started, Windows Installer can check whether the keypath of any component is missing. If the keypath is missing, the component is reinstalled/repaired. If a component has multiple files, then only one file can be the keypath. In wix you indicate this by setting KeyPath=yes on

问题 I found an example on registering DLLs, Registering an Assembly for COM Interop in a MSI file with the Windows Installer XML toolset. , and WiX complains about the \"AssemblyRegisterComInterop\" attribute. I removed that and changed the \"Assembly\" attribute to win32, and it says I need to specify the AssemblyManifest attribute, but what should I put there? 回答1: The easiest way (and Rob M will rant and rave about how this is wrong ) is just to use SelfRegCost=1 on the File tag for the DLL.

问题 We have an installer which requires a reboot on install, but it is also rebooting on uninstall. Is there a way we can prevent the reboot when uninstalling? This is what we have at the moment: <InstallExecuteSequence> <ScheduleReboot After=\"InstallFinalize\"/> </InstallExecuteSequence> Many thanks in advance! 回答1: Restart Manager : The Restart Manager Feature of Windows (Installer) (middle page) is designed to help restart applications automatically during installation rather than requiring a

问题 We\'ve been using WiX for a while now, and despite the usual gripes about ease of use, it\'s going reasonably well. What I\'m looking for is useful advice regarding: Setting up a WiX project (layout, references, file patterns) Integrating WiX into solutions, and build/release processes Configuring installers for new installations and upgrades Any good WiX hacks you\'d like to share 回答1: Keep variables in a separate wxi include file. Enables re-use, variables are faster to find and (if needed)

问题 When should I change or not change my component GUID in WIX? The Microsoft SDK information is confusing. Glytzhkof edit : To clarify, the question deals with when a component GUID should be changed for an MSI component. A component can change with aspects such as: changed destination path, addition or removal of files to/from the same component, addition of registry data etc... This causes problems with regards to the so called component referencing, i.e the best practice for creating