windows-installer

问题 I am really very sorry for being redundant. I have checked a lot of other posts in this site itself and perhaps some other sites. I am not able to get Major Upgrade working without uninstalling & reinstalling of service. I am changing the Product Code and Version and the UpgradeFileComponent is the component that is part of the Upgrade. All the remaining are the same as in 1.0.0. I am doing a POC and hence would like to make only this small change (not as a patch, but as a major upgrade).

问题 I have a visual studio installer (vs2015) that installs an application. I want it to also install a set of configuration files, the contents of which vary by physical install location, that will be delivered as a cab file in the same directory as the msi. The cab has a known set of files that will be distributed across 2 folders in the install location and is created by a different project than the installer. How do I get the msi to install both its internal contents and the contents of the

问题 This question already has an answer here : Uninstalling program (1 answer) Closed last year . As shown in the picture I've retrieved the uninstallstring of an application. And this is the code which I'm trying to make that application uninstall. uninstlString = Convert.ToString(subkey.GetValue("UninstallString")); if (uninstlString.Contains("MsiExec.exe")) { //Console.WriteLine(uninstlString); //Console.ReadLine(); string args = "/x{" + uninstlString.Split("/".ToCharArray())[1].Split("I{"

问题 I stuck on problem with wix installer. My idea is create .msi installer, and then user install .msi , the setup.exe runs , and then user close this setup.exe(setup will install microsoft add-in) the second one(picture) will be opened sequently. Now this code below runs after checkbox is ticked two aplications both at once. Is the way to run picture only when closed first one ? Please suggest! Here is my code: <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix

问题 I have a couple of features in my setup. I have also enabled the Change option. i.e. A user can change what s/he want's to install or uninstall after the initial install. When a feature is removed using this Change option it gets uninstalled. I would have expected the size of installer to be reduced but it stays the same. Now when the feature is later added using Change option the overall size of ths installer is increased. Is there a way to control this or does it always work like this? Note

问题 I have two features: <Feature Id='BaseProductFeatures' Title='Feature 1' Level='1'> <ComponentRef Id='WebAppVDirComponent'/> <ComponentRef Id='someVDirComponent'/> <ComponentRef Id='anotherWCFVDirComponent'/> <ComponentGroupRef Id='group_IMPORTFOLDERFILES'/> <ComponentGroupRef Id='group_WINSERVERFILES'/> </Feature> <Feature Id='SMSGWFeature' Title='Feature 2' Level='2'> <ComponentGroupRef Id='group_SMSGWWEBAPPFILES'/> </Feature> Before the install, I change the INSTALLLEVEL to 2 using a

问题 I'm building an install using VS 2003. The install has an Excel workbook and two Access databases. I need to force the Access files to load regardless of the create/mod date of the existing databases on the user's computer. I currently use ORCA to force in a Version number on the two files, but would like to find a simpler, more elegant solution (hand editing a .msi file is not something I see as "best practice". Is there a way to add a version number to the databases using Access that would

问题 I'm trying to deploy and distribute a C++ app on Windows. I've managed to create an MSI installer with Visual Studio (with the Microsoft Visual Studio Installer Project extension). When I run it on my computer, everything is fine. But if I run it on someone's else computer, Windows Defender displays a SmartScreen warning: We are still in beta, so we don't have a lot of money or any certificates, but we want to make the beta available without this warning to allow users to test the product and

问题 I use a program called MSICREATE to generate msi packages for a piece of software. I then use orca to transform the msi package. Things work ok but users must delete the existing product before installing an update. I'd like to modify the msi package so the installer recognizes a newer or different version is being installed and removes the current version and then installs the new msi package. What property table entries are needed? ========= The answer given below has helped me get beyond

问题 I'm using WIX to create a new installer for an existing product. The installer is very simple - just drops a few dll's into a specified folder on disk. In the field, my users already have that folder with old dll's in them (since they installed the old MSI - created using a *.vdproj project in VS). My problem is that after I install the WIX, I have both the old MSI and the new Wix MSI appear in Add/Remove. Expected (? since these 2 are two different kind of MSI's?). I need some kind of an