installshield

问题 I'm using InstallShield to install my application, a driver and a service. I need to install the plug-N-play driver only if it's hardware ID was found in the device manager. The driver installation is done using DPInst.exe. My problem, is that a user can sometimes manually uninstall the driver (After it was installed or even uninstall the "Unknown driver" under "Other devices" ) and then I can't find the hardware ID in the device tree, although the device is plugged. If I rescan the device

问题 I am creating a Basic Msi Installer using Installshield 2012 spring professional . Here i create a folder structure in Application Files as C:\Program files\Test Setup\Productname , Test Setup is the INSTALLDIR , and within this i have sub directories one of which [launch] contains the exe files . I have added these files and the directory sturcture using the Add Files and folders option in Application files menu of Project Assistant. After installing the product , when i uninstall it i find

问题 I have an old VB6 application that is deployed using a very old 16 bit version of InstallShield. I have created a new installer with Inno Setup to be 64 bit friendly for my VB6 application with updates. All of my users already have the existing InstallShield version installed. Currently, I have Inno Setup working. The problem is, I do not want to overwrite the old InstallShield installation files, so my Inno Setup installs to another directory. This causes problems because now I have two

问题 I have seen many solutions for automating my InstallShield build, but I am having issues with each one. I am using InstallShield Professional 2013. Sorry for the lengthy question, but I am clueless on which direction to go to solve my issues. 1) IsCmdBld.exe - I have a script that runs and will build my installer. BUT, when the installer runs, I get an error message that says "The System Administrator has set policies to prevent this installation" . I am not sure why this is happening, but I

问题 I wrote a windows service that runs on Framework 4.0 and running in VS 2015. I also created a setup project (free Installshield version). My service did not show under services.msc after I installed it, so according to some other posts I had to mark the Primary Output in InstallShield as 'Installer Class', but when I do that I get Error 1001 when I run the setup.exe. This post states that "Error code 1001 ALWAYS means a failure in the Installer class custom action." and that I should not use

问题 I wrote a windows service that runs on Framework 4.0 and running in VS 2015. I also created a setup project (free Installshield version). My service did not show under services.msc after I installed it, so according to some other posts I had to mark the Primary Output in InstallShield as 'Installer Class', but when I do that I get Error 1001 when I run the setup.exe. This post states that "Error code 1001 ALWAYS means a failure in the Installer class custom action." and that I should not use

问题 I need to run a custom action only during Repair. But I didn't find a valid condition to do so. If I specify a custom action with below condition, it runs in Modify mode as well as in Repair mode. Installed AND Not REMOVE I am using InstallShield 2012 spring. 回答1: Check the REINSTALL property. Conditional statement on your custom action should look like REINSTALL<>"" 回答2: For future reference check these cheat sheets: Installshield condition cheat sheet. How to add a WiX custom action that

问题 How do I avoid distributing sensitive information in my WiX / MSI by accident? I distributed a password, machine name or login credentials by accident with my MSI file. How do I best deal with this problem? After deployment my application connects erronously to my QA / UAT systems instead of my production systems - because of a faulty debugging construct in my setup's custom action code. How can I detect and avoid this? How do I avoid distribution such information in general? This is a Q/A

问题 I'm designing a new MSI installation for a product that allows multiple instances to be installed. Many of the components of the installation are identified by a 2-character code. Among these is an ODBC data source. The name of the data source includes this 2-character code, which is something the user enters during installation. I notice that I cannot use a property name "[MyPropertyName]" as the Name of an ODBC DSN in an InstallShield project. Is there any clean way to allow the ODBC DSN

问题 I'm designing a new MSI installation for a product that allows multiple instances to be installed. Many of the components of the installation are identified by a 2-character code. Among these is an ODBC data source. The name of the data source includes this 2-character code, which is something the user enters during installation. I notice that I cannot use a property name "[MyPropertyName]" as the Name of an ODBC DSN in an InstallShield project. Is there any clean way to allow the ODBC DSN