installer

问题 I'm using Wix 3.5 to build a MSI installer. I want to know if there is any way to hide some options from the "Features Custom Setup dialog" (in which you select from the Feature tree what to install). I want to only have the options for "Will be installed on local hard drive" and "Entire feature will be unavailable" Currently, apart from those two options i have these options: "Entire feature will be installed on local hard drive" "Will be installed to run from network" "Entire feature will

问题 After a lot of research I have to ask you guys in order to get my project finally running. I want to save data which the user puts into a TextBox of the Visual Studio Project Installer to a text file. I have read different articles, also this one: C# Visual Studio Project Installer retrieve data from Textbox But the question was not answered there so I'm asking you to get this question finally solved. And please give me a Code example where it is written in C# Code how to get this values from

问题 I'm using some app called pgModeler and it's current version provides an installer based on QT installer framework. The problem with that installer on Windows is that it installs start menu entries per-user only and registers the app itself per-user only as well. That's a problem for people like me using an explicit admin-user for system maintenance vs. a non-admin user for daily work. The important thing is that really two different user names are used ( Administrator vs. tschoening )

问题 I currently have two WIX installers for a product that I maintain. One for 32-bit operating systems, and one for 64-bit operating systems. Instead of maintaining two separate installers, I want to combine them into one NSIS installer that can "determine" the "bitness" of the OS and then copy the appropriate binaries into the program directory. Has anyone had any experience with this and could provide a working sample script that NSIS can use to make the installer? 回答1: x64.nsh has some helper

问题 I currently have two WIX installers for a product that I maintain. One for 32-bit operating systems, and one for 64-bit operating systems. Instead of maintaining two separate installers, I want to combine them into one NSIS installer that can "determine" the "bitness" of the OS and then copy the appropriate binaries into the program directory. Has anyone had any experience with this and could provide a working sample script that NSIS can use to make the installer? 回答1: x64.nsh has some helper

问题 I hit numerous errors in Wix 3.0 when I tried to use the msvbvm60.msm merge module: C:\[...]: error LGHT0204 : ICE03: Table: Registry Column: Registry Missing specifications in _Validation Table (or Old Database) C:\[...]: error LGHT0204 : ICE03: Table: Registry Column: Root Missing specifications in _Validation Table (or Old Database) C:\[...]: error LGHT0204 : ICE03: Table: Registry Column: Key Missing specifications in _Validation Table (or Old Database) C:\[...]: error LGHT0204 : ICE03:

问题 I am new to Wix Installer. I have a requirement where I have to provide credentials for SQL Server login and run a script from a specific path. I am not getting what's going wrong.The project is build successfully and .msi is created. After running it I get the following Error: Error 26204. Error -2147217900: failed to execute SQL string, error detail: Incorrect syntax near '»'., SQL key: CreateUpsizingDatabase SQL string: print convert(varchar(25),GetDate(),121) + ' Executing file:

问题 I'm writing an installer that will tune the configuration of the product for the particular hardware on which it will be run. In particular, I want to determine how much physical RAM is installed in the system so I can estimate how much memory to allocate to the product when it runs. Ideally, I'd like to do this in a platform-independent, pure Java way, as the installer will need to run on several different platforms, but in case this isn't possible, solutions for Windows are preferred as

问题 In WiX DirectorySearch can be used to determine if a specific directory exists on the target computer. But I don't understand if there's a consistent way to determine that a directory does not exist. For example: <Property Id="INSTALLDIR" Secure="yes"> <RegistrySearch Id='InstallDir' Type='directory' Root='HKLM' Key='Software\Company\Product\Install' Name='InstallPath'/> </Property> <Property Id='IS_INSTALLED' Secure='yes'> <DirectorySearch Id='IsInstalled' Path='[INSTALLDIR]' /> </Property>

问题 I have a night build which runs on different machine then mine on my machine i can compile the installer and use the msi without a problem however on the night build machine i get C:\Builds\73\Tools\AppInstaller\src\AppInstaller\APPExportReleaseDir.wxs (693): ICE03: Invalid Language Id; Table: File, Column: Language, Key(s): filAAED19CB2C0BBE304CDB8EB1AAF7473F The file which is showing that is system.windows.interactivity.xml Can you please explain what are ICE03 errors and how can I fix this