windows-installer

问题 I have merged msm for vs 2015 crt: <DirectoryRef Id="TARGETDIR" > <Merge Id = "Microsoft_VC140_CRT_x64.msm" FileCompression = "yes" Language = "1033" SourceFile = "..\\..\\..\\..\\..\\..\\..\\external\\tools\\systemsetups\\merge_modules\\Microsoft_VC140_CRT_x64.msm" DiskId = "1" />" </DirectoryRef> <Feature> <Feature Id="Complete" Title="Complete" Absent="allow" Level="1"> ... <MergeRef Id="Microsoft_VC140_CRT_x64.msm"/> ... </Feature> but I still receiving: --------------------------- MyApp

问题 In my WIX project I have a directory structure something like this: <Directory Id="TARGETDIR" Name="SourceDir"> <Directory Id="INSTALLLOCATION" Name="FolderName"> ... </Directory> <Directory Id="MYDIRECTORY" Name="SomeDifferentDirectory"> ... </Directory> </Directory> Here INSTALLLOCATION represents the installation folder of my program, but I want to additionally create another directory that is outside the installation directory, for example, D:\MyFolder1\MyFolder2 , from the example above

问题 I have the dreaded issue from my attempted installation of an MSI: MSI (c) (98:B0) [18:01:22:818]: Invoking remote custom action. DLL: C:\DOCUME~1\sspencer\LOCALS~1\Temp\1\MSI19.tmp, Entrypoint: CheckFX MSI (c) (98:FC) [18:01:22:833]: Cloaking enabled. MSI (c) (98:FC) [18:01:22:833]: Attempting to enable all disabled privileges before calling Install on Server MSI (c) (98:FC) [18:01:22:833]: Connected to service for CA interface. Action ended 18:01:22: DIRCA_CheckFX. Return value 3. After

问题 How do I avoid distributing sensitive information in my WiX / MSI by accident? I distributed a password, machine name or login credentials by accident with my MSI file. How do I best deal with this problem? After deployment my application connects erronously to my QA / UAT systems instead of my production systems - because of a faulty debugging construct in my setup's custom action code. How can I detect and avoid this? How do I avoid distribution such information in general? This is a Q/A

问题 I am trying to write a .bat for the first time. I am trying to install .msi using script, currently we are installing manually by double clicking on it. Path from : d:/installed sw/$folder/.msi Path to : D:/program files/app/ $folder means, it is different every time, as we are getting new msi to install which are provided in folder created by current date. Here is the script I am trying: @echo off Title HOST: Installing Updates on %computername% echo %computername% set server=\\SERVERNAME or

问题 This is probably a stupid question and my Googling just is not functioning today. I have an application I added a Visual Studio Installer > Setup Wizard project to. I am wondering how to add a button or check box that would launch the application after successful install. This would be located on the last page of the MSI Installer Package. I am using Visual Studio 2010 Ultimate. I am needing this so that when the application does an automatic update, it auto launches the installer. I just

问题 I have a installer which is working fine. I want to run custom action only in install and modify only. Here is my custom action: <Custom Action="UpdateAPMDBAPasswordAndStoreInRegistry" After="InstallFinalize"><![CDATA[&BaseModel = 3 OR &FeaturePostMaster = 3]]></Custom> The above custom action is not running when modify the the installer. It runs only when install the installer. After googled, i did this but it is also not working: <Custom Action="UpdateAPMDBAPasswordAndStoreInRegistry" After

问题 We use wix to create our setups. For upgrading, we use major upgrades as demonstrated in this answer by Rob Mensching. (In newer wix versions you can use the MajorUpgrade element.) This normally works well. The old product is removed, then the new product is installed. However, apparently the above is not completely equivalent to manually uninstalling the old product and then manually installing the new product. Consider for example the following scenario: version 1.0 of our product is

问题 Windows Installer self-repair can cause problems for both developers , system administrators and end users . Finding the solution can be difficult if you have limited MSI experience. This is a Q&A-style answer intended as a check list for solving self-repair problems . Here are a few common problem scenarios: Repeated Windows Installer self-repair might occur whenever you launch an application on your workstation. How can this be fixed, or how can components be disabled so it never occurs

问题 I want to packed up my winform project by Inno Setup. But in addition to the main executable, it must specify the other required files and there are many files in the project folder. So which files is required? Does .cs scripts important? Or just the files in /bin/release/? 回答1: Overall : I like Tom Blodget's advice here to find dependencies and runtimes. Below are some detailed, technical options to determine what is going on with problem applications. Assembled in a hurry. Clean Virtual :