windows-installer

问题 I have an MSI that setups my application. It has a single component and installs only to %PROGRAMFILES% (no shared binaries). Simplified, it looks like this Msi file, Monday build: Program.exe (v1.0.0) ThirdPartyLibrary.dll (v2.0.1) Now, if I discover a bug in the program caused by my upgrade of the ThirdPartyLibrary dll from v2.0.0 to v2.0.1, and thus revert the reference to v2.0.0, it seems my MSI doesn't automatically replace the file in the installation directory? Msi file, Tuesday build:

问题 I am going to create setup for my web project. I use http://blog.bartdemeyer.be/2013/10/create-an-installer-for-website-with-wix-part-1/ as my reference. In the middle of article, author create a file called WebSiteContent.wxs using heat.exe: <Target Name="Harvest"> <!-- Harvest all content of published result --> <Exec Command='$(WixPath)heat dir $(Publish) -dr INSTALLFOLDER -ke -srd -cg MyWebWebComponents -var var.publishDir -gg -out $(WebSiteContentCode)' ContinueOnError="false"

问题 I am writing an installer for my web app and I struggle with the uninstaller part. Despite the fact that I created a custom action on Uninstall in my Application Setup Project, the InstallerClass is set to true, the method: public override void Uninstall(IDictionary savedState) { //MessageBox.Show("Attach debugger!", "Viper.Setup"); Cleanup(); base.Uninstall(savedState); } on the installer class doesn't seem to be called. Any ideas what could be the reason? EDIT: I also noticed that it not

问题 I used bdist_msi from cx_freeze in the past and it works nice. Now I need to create registry entries Is it possible to create registry entries with bdist_msi from cx_freeze? With the wixtools these settings were done in the past: <!-- File extension .foostarter --> <RegistryValue Root='HKCR' Type='string' Key='.foostarter' Value='foostarter.File' /> <RegistryValue Root='HKCR' Type='string' Key='.foostarter' Name='Content Type' Value='application/vnd.foobar-modstarter' /> <RegistryValue Root=

问题 In my installer, I have two optional features, which are plugins for versions 5 and 6 of the same software. They install the same file (same name, same binary content) into the "plugins" folder of the applications. But I have the following error: C:\Users\FooBar\Documents\project\project.wxs(281) : error LGHT0204 : ICE30: The target file '0egx-0x3.dll|appv5plugin.dll' is installed in '[TARGETDIR]\plugins\' by two different components on an LFN system: 'Comp_ThisAppV5_plugin' and 'Comp

问题 I'm using this code to return a FileContentResult with an MSI file for the user to download in my ASP.NET MVC controller: using (StreamReader reader = new StreamReader(@"c:\WixTest.msi")) { Byte[] bytes = Encoding.ASCII.GetBytes(reader.ReadToEnd()); return File(bytes, "text/plain", "download.msi"); } I can download the file, but when I try to run the installer I get an error message saying: This installation package could not be opened. Contact the application vendor to verify that this is a

问题 I'm trying to convert the MSI product code GUID into the product code ID used to identify the installed item in the MSI registry keys. Is there an API for this? If not, how can this be done? 回答1: Warning! Microsoft strongly recommends that you don't mess with their MSI Registry keys, but if you really must, here is a routine to translate a standard product code GUID to the key format used in the registry: private static string TranslateMsiProductCode(Guid productCode) { // 93 CE EF F6 AA 3D

问题 The MSI stores the installation directory for the future uninstall tasks. Using the INSTALLPROPERTY_INSTALLLOCATION property (that is "InstallLocation" ) works only the installer has set the ARPINSTALLLOCATION property during the installation. But this property is optional and almost nobody uses it. How could I retrieve the installation directory? 回答1: Use a registry key to keep track of your install directory, that way you can reference it when upgrading and removing the product. Using WIX I

问题 I'm trying to install Visual Studio 2013 Express for Desktop on a Windows 7 Pro machine. I've downloaded the ISO file and I'm running that locally. I run the installer and get an error about certain prerequisites not being installed (the C++ runtimes for one). I've downloaded all the prerequisites, but when I try to install the Visual Studio 2013 Shell (Isolated) I get the following error rather unhelpful message: Fatal error during installation. However, checking the log file reveals the

问题 I am very new to PowerShell and have some difficulty with understanding. I want to install an .MSI inside PowerShell script. Can please explain me how to do that or provide me beginners level tutorial. $wiObject = New-Object -ComObject WindowsInstaller.Installer ????? 回答1: Why get so fancy about it? Just invoke the .msi file: & <path>\filename.msi or Start-Process <path>\filename.msi Edit: Full list of Start-Process parameters https://ss64.com/ps/start-process.html 回答2: #Variables