windows-installer

问题 I have created a setupkit with no UI using Wix for my application (called "XYZ" here). If I double click the MSI while XYZ.exe is runnning, it notifies me that a process is locking a file: I can choose to kill the locking process or I can abort the installation. This is fine: as a user I can decide what to do. But when I run the same MSI from the commandline, msiexec /i XYZ.msi /quiet /norestart if XYZ.exe is found running it will be killed. This is absolutely inacceptable in my scenario: the

问题 I am trying to add my own help file to Visual Studio 2010's Help Library by using WiX to run the HelpLibraryManagerLauncher that the Sandcastle Help File Builder creates after it builds my Sandcastle project. I am using WiX's QuietExec custom action to run the following command: HelpLibraryManagerLauncher.exe /product "VS" /version "100" /locale en-us /silent /brandingPackage Dev10.mshc /sourceMedia MyClassLibraryHelp.msha However, the MSI installer fails with the following: Action 00:00:00:

问题 I need to install redistributable Visual C++ 2015 on three hundred computers in a corporate office. Is there any way to convert EXE to MSI. It would save tons of time. 回答1: The Visual Studio 2015 and 2017 installers are built with the WiX toolset. You can extract the contents of these with the dark tool: +>dir /b vc_* vc_redist.x64.exe vc_redist.x86.exe +>mkdir x64-extracted +>c:\local\WiX-3.11.1-bin\dark.exe vc_redist.x64.exe -x x64-extracted Windows Installer XML Toolset Decompiler version

问题 I have an NSIS installer executable which I would like to install silently for all users. I know I can pass the /S argument to do a silent install. The problem is that the default option for the installer is to install only for the current user. How can I change this option from the command line: installer.exe /S 回答1: NSIS itself just supports /S , /NCRC and /D=c:\override\default\installdir\ , everything else is up the author. If the custom page from your screenshot was created with

问题 I use Wix Toolset v3.11 to generate an .msi installer for my Windows application. How can I have a publisher name appear in the entry for my application in Settings -> Apps & features ? I noticed that some entries in that list include a publisher name underneath the app name: I set <Product ... Manufacturer="My Company Name" ... in my .wxs file and I can see this is stored in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\<guid>\Publisher .

问题 This is Visual Studio 2015 Community Edition. I'm using Setup Project (MSI) to create an installer for my VSTO add-in. I have done this stuff numerous number of times in previous versions of VS and haven't ever seen this behavior. VS2015 detects a huge number of dependencies that aren't included in the references of the add-in project. Rebuilding the projects and using Refresh Dependencies command hasn't proved any good. Has anyone else experienced this problem or knows a solution? Here's a

问题 What is the difference between using an MST combined with an MSI, and running the MSI and passing the modified properties through the command line (MSIEXEC) 回答1: An MST can contain all kinds of changes to the MSI--including new or different files, Registry entries, custom actions... and modified properties, as you mention. On the MSI command line, the only thing you can do differently is change properties... 回答2: When deploying a package via Active Directory, you can't specify command line

问题 When I run my MSI on a Windows 2012 R2 machine (RTM build 9600) the VersionNT property is set to 602 (instead of 603). If 602 is actually the correct OS version, then how to I programmatically differentiate between Windows 2012 and Windows 2012 R2 at install time? Update: It looks as though if I run my MSI directly on Windows 2012 R2 or Windows 8.1, VersionNT will be, correctly, set to 603. If my MSI is kicked off by a bootstrapper (a win32 app), VersionNT will be set, incorrectly, to 602. So

问题 For my application, I need to install the main application and allow users to pick and choose one or more additional features to install. I tried to run the main msi and have a custom action to install other feature msi files. However, it doesn't work since MSI doesn't support nested installation. Should I build a window application and give the users the choices and internally call msi files sequentially? The additional msi files are custom applications that we built. They are not pre

问题 After review a lot of posts in this site finally I decide to put mine. I am preparing an MSI file with Wix. I need to check if a particular version of an enterprise product is installed, before to install my system. I have the GUID of that product (which is the same for all versions), but I need to check if 1.10.0 version is installed. Any idea, please. Thanks in advance. PD: I am newbie in Wix, so at this moment I am just using the wxs file created by default with the Setup Project.