windows-installer

问题 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

问题 I know you can change it using cscript.exe on Windows. Is there a Linux program providing cscript-like functionality? Or is there some other way I can change the database in Linux? 回答1: CScript is just the script execution engine; it knows nothing about MSI directly. Check out Wine; it implements some/most of msi.dll, so as long as functions like MsiDatabaseOpenView and MsiViewExecute are correctly implemented, you should be able to use it to modify an .msi package. 来源： https://stackoverflow

问题 I developed a project on VS 2010 using c++ qt. When I run the project in debug or release mode it works great. But what I want is to run it by double clicking on the generated executable, unfortunately when I do that I get a R6010 Error .. abort has been called. I want to solve this problem to help me creating an installer for my project. Thank you in advance. 回答1: It happened to me exactly the same, and the problem was that the executable was reading a configuration file and some image files

问题 I'm about to create an installer, now i have to set the install-directory depending on the operation-system. My directory-tree: <Property Id="TARGETDIR" Value="C:\" /> <Directory Id="TARGETDIR" Name="SourceDir"> <Directory Id="TARGETDIRECTORY" Name="MyApplication"> <Directory Id="CONFIG" Name="Config"> <Directory Id="FOLDER2" Name="Folder2" /> </Directory> </Directory> </Directory> if i set the TARGETDIRECTORY in the c#-custom-action, the targetdirectory gets set correct, but the CONFIG

问题 I'm about to create an installer, now i have to set the install-directory depending on the operation-system. My directory-tree: <Property Id="TARGETDIR" Value="C:\" /> <Directory Id="TARGETDIR" Name="SourceDir"> <Directory Id="TARGETDIRECTORY" Name="MyApplication"> <Directory Id="CONFIG" Name="Config"> <Directory Id="FOLDER2" Name="Folder2" /> </Directory> </Directory> </Directory> if i set the TARGETDIRECTORY in the c#-custom-action, the targetdirectory gets set correct, but the CONFIG

问题 We are using Wix to build msi for our software. We have some components (plugins) to be implemented to the target machine. The plugins are different from one client to another. What we want to be able to do is to create a standard build and modify the feature list in the msi package. Is there a way to change the feature list dynamically from a custom action? (e.g. read the available plugins from a custom action and add some entries into the msi feature list accordingly)? Any comments, advice,

问题 I am trying to programmatically find the exe file that is run for a given MSI lnk file (advertised shortcut). I have used an approach similar to that shown in the answer to Is there a way to resolve a .lnk target that works for links that end up in c:\windows\installer?. This approach works fine for the majority of MSI lnk files. Unfortunately there are a minority of lnk files that run fine, but MsiGetShortcutTarget returns no component id. So the subsequent call to MsiGetComponentPath

问题 I am a C# developer who is bundling a colleague's VBA Excel Add-In (.xlam file) with my msi installer (built using a VS Deployment project if that matters). The .xlam is placed in the application folder (C:\Program Files (x86)\MyCompany\TheProduct) directory. Users are forced to navigate to Excel Options > Add-Ins > Manage Excel Add-Ins Go... > Browse and are then forced to navigate to the install directory listed above. The Browse screen default directory is %APPDATA%\Microsoft\AddIns. Is

问题 When using a legacy VB6 application and opening some specific forms inside that application, the Windows Installer belonging to Microsoft Navision (which is installed on the same machine) pops-up like in the attached image. It happens every time, but on this machine only. The VB6 application has absolutely no relation with Navision! What can be done to avoid this anomalous interaction between the two applications? 回答1: This is down to a corrupt windows installer database and your app is using