installshield

问题 I have a basic MSI InstallShield installation with a managed EXE custom action running from the Binary table. I tried a simple test that just runs a console and that works fine. When I add a .DLL assembly reference to the EXE, it can't find the DLL. How do I make InstallShield aware of this referenced assembly so it can load it with the EXE? 回答1: Custom Actions only extract a single file to a temporary location under a temporary name. For the dependency on the .dll to work, they need to both

问题 I have a basic MSI InstallShield installation with a managed EXE custom action running from the Binary table. I tried a simple test that just runs a console and that works fine. When I add a .DLL assembly reference to the EXE, it can't find the DLL. How do I make InstallShield aware of this referenced assembly so it can load it with the EXE? 回答1: Custom Actions only extract a single file to a temporary location under a temporary name. For the dependency on the .dll to work, they need to both

问题 I am creating an install package using InstallShield Pro X. The upgrade works properly. However, the product manager wants the upgrade to replace all files on an upgrade even if the create date != modify date on the file. I see that to do this I need to set REINSTALLMODE=vamus rather than vomus. However, I don't see how to tell InstallShield that I want it to use that setting. By default setup.exe always passes vomus to windows installer. There is a property in the InstallShield project named

问题 I want to run my exe after installation using InstallShield. InstallShield completes the setup correctly but do not run the exe. I found another way to add an exe in startup but it runs after restart. I would like it to run without restart. Is it possible ? 回答1: What version and edition of InstallShield are you using? Also what project type are you using? (InstallScript, InstallScript MSI, Basic MSI? ) Assuming Basic MSI, InstallShield has a built-in pattern to support this story: 1) Click on

问题 As you see from Project Assistant->Installment Requirement screenshot of InstallShield , It is showing only till .NET Framework 4.6 in the list. How do I add other frameworks like 4.7 and above? 回答1: You will have to create your own custom prerequisite. Just look at all the settings for 4.6, copy them to the new prerequisite and modify accordingly (e.g. registry entries, file paths etc.) to reflect the new version. To verify registry entries and file paths, you will need to have .NET 4.7

问题 I created the MSI build package for our application. After this installation, we triggered another dependent driver software in the separate process in a committed event of Installer class like below, Process.Start (" Path of driver software ") We are facing an issue, installed directory ( It's empty ) folder is not removing while un-installing the same. Actually like installation, we triggered the un-installation of dependent driver software in the separate process by overriding the

问题 I am using Limited Edition of InstallShield 2015 with Visual Studio 2015. I have configured Internet information Services settings as shown below, but website is not getting created in IIS. My IIS version is: 10.0 Here is the IIS settings inside InstallShield Note: Source code is successfully copies [INSTALLDIR] of destination computer but it's not getting mapped with IIS. Updates I see only declaration related to IIS, but not used anywhere in log! Property(S): PROGMSG_IIS_CREATEAPPPOOL =

问题 How can I log only the changes causing a MSI file made by Installshield 2008 to reinstall via " self-repair "? What is the reason behind self-repair? How do I disable self-repairing of MSI using Installshield 2008? 回答1: Self-Repair, Simple & Short Explanation : Why does the MSI installer reconfigure if I delete a file? Alternative Answer Available UPDATE : There is a shorter, more "solution focused" answer available, perhaps try it first. This answer focuses on "understanding self-repair"

问题 How can I log only the changes causing a MSI file made by Installshield 2008 to reinstall via " self-repair "? What is the reason behind self-repair? How do I disable self-repairing of MSI using Installshield 2008? 回答1: Self-Repair, Simple & Short Explanation : Why does the MSI installer reconfigure if I delete a file? Alternative Answer Available UPDATE : There is a shorter, more "solution focused" answer available, perhaps try it first. This answer focuses on "understanding self-repair"

问题 I have created a com addIn in Visual Studio Tools for Office (VSTO) for Excel 2010 and I want to create a single exe setup file for end user. I have googled this issue but all I can find are the solutions using Visual studio. I want to create setup with Installshield program. 回答1: The process is described here in details for InstallShield Limited Edition (it should be very similar to Installshield 2008). It is a standard installation procedure except for 2 important points : You must ensure