wix

问题 I'm really struggling with WiX. I have .NET assemblies to install that require registration for COM Interop, AND they must be registered with another framework that requires calling a Register() method in a .NET assembly that's in the GAC. This registration method is a 'black box' with a hidden storage mechanism so I can't perform this operation declaratively. I get that the declaritive approach is best for COM registration, but I have two problems with using heat.exe: RegAsm works, but Heat

问题 I have a wix installer that will install an XML file and then modify it. Installation works great. Today, I needed to add a couple of nodes to this XML file. So I modified the original file and then added some additional instructions to wix to assign these items values. Well, I get an error every time saying that it cannot find the node. I look and see what file it has in the directory and it still has the older file that did not have the node. How can I tell it to replace the XML file first

问题 I'm trying to show a custom status message in default wix's ProgressDlg, following this answer: WiX: dynamically changing the status text during CustomAction So far, I got this code in my custom action: public class CustomActions { [CustomAction] public static ActionResult CustomAction1(Session session) { Debugger.Launch(); session.Log("Begin CustomAction1"); MessageTest(session); return ActionResult.Success; } private static void MessageTest(Session session) { for (int i = 0; i < 10; i++) {

问题 I would like to protect the MSI file against modification. It could be easily done with ORCA or with MSI API. It is sad because anyone can modify/add/remove windows installer custom actions or properties who have admin rights. Is there any way to set an MSI file to some read-only mode or somehow protect its content? 回答1: The short answer is no, you cannot prevent someone from editing a .msi file. There are various approaches you can take to minimize the likelihood of someone doing so, or

问题 I have a WiX based MSI that installs a service and some shortcuts (and lots of other files that don't). The shortcut is created as described in the WiX docs with a registry key under HKCU as the key file. This is an all users install, but to get past ICE38, this registry key has to be under the current user. When the service starts (it runs under the SYSTEM account) it notices that that registry key isn't valid (at least of that user) and runs the install again to "repair". In the Event Log I

问题 I have a WiX based MSI that installs a service and some shortcuts (and lots of other files that don't). The shortcut is created as described in the WiX docs with a registry key under HKCU as the key file. This is an all users install, but to get past ICE38, this registry key has to be under the current user. When the service starts (it runs under the SYSTEM account) it notices that that registry key isn't valid (at least of that user) and runs the install again to "repair". In the Event Log I

问题 We are working on creating an installation package for a WCF-based web service. The service uses message-level encryption via an installed certificate. I am trying to come up with an automated way to both install the certificate and set its permissions. Currently, we are manually installing the certificate via the MMC snap-in. After it is installed, we need to find the file containing the installed certificate and modify the permissions so that the Network Service account can access it. The

问题 The questions regarding Bootstrapper & Chaining might have been asked before. I am trying to ask something similar & different . My requirement is to CHAIN 3 installshield msi into a single one and expose the feature selection GUI of 2 of the MSIs as a single feature set such that when the user selects any of the features on the top-level, that selection is passed as parameter(s) to the underlying respective msi & installation continues. User may launch this exe / setup again where he can

问题 I have web app, which I want to install on IIS. This app supports plugins architecture. It consists of: Core Part Plugin A Plugin B I want to have 2 installers (msi). One for plugin A and other for plugin B. Each installer should also install Core Part. So if I run installer for plugin A it should install Core Part and Plugin A binaries. Then if I run Installer for plugin B it should install only Plugin B binaries. But if run installer for Plugin B as first it should install Core Part and

问题 There is a Burn Built-in Variable - WixBundleDirectoryLayout. How can I assign a value to this variable to change where the bundle extracts to? I also tried running... setup.exe /layout c:\temp ...from a command line and it just copies the setup.exe file to c:\temp, instead of actually extracting the bundle contents. What am I doing wrong? 回答1: The /layout switch does not extract the contents of a Bundle. It downloads all the content and creates an image that you could then burn to DVD or put