installshield

I implemented an installscript file of my own that will allow the installer to register dll's. I combined this with a custom action to actually run the function I created. I had to make this script because the dlls were failing to register with setting the property to self register. So I am stuck on how to resolve this problem with the custom action failing so that I can test my script. Below is my script: #include "Ifx.h" export prototype RegisterComponents(HWND); function RegisterComponents(hMSI) STRING sRunStr; begin sRunStr = WINSYSDIR ^ "regsvr32.exe"; LongPathToQuote(sRunStr, TRUE); /

I have a Basic MSI Install with Install Shield 2013 and we have about 20 different affiliate releases. Really the only difference between these releases is the Program Name and the shortcut that is installed on the desktop. We are trying to have one release build instead of building the same program over and over with these minor differences. I have been trying to find a way to change those items at install time but have not been successful. Has anyone out there done this before or have any suggestions of where I could find some information about things like this. My goal for the user

I am developing a Winforms app using C# and VS 2010. This app will use a SQLite database that will be deployed with the initial installation of the app. When I have new releases of the app, how do I tell Installshield not to touch this file? If the user uninstalls the app, it is ok to remove this file, but when they are upgrading from 1.0 to 1.1 etc, I can't overwrite this file. This is usually done through backup and restore custom actions and it's not supported by InstallShield LE. Basically, a custom action creates a backup before the old version is uninstalled and another custom action

I have one feature with several components. One components contains dynamic linked files in a directory. When I delete one file in that directory, build the setup, and run the upgrade, no file will be replaced. In the log I found this error: MSI (s) (5C:D8) [12:28:41:180]: SELMGR: ComponentId '{8F4E8185-5B89-9FC9-9FD5-3200102A0265}' is registered to feature 'MyFeatureName', but is not present in the Component table. Removal of components from a feature is not supported! MSI (s) (5C:D8) [12:28:41:180]: SELMGR: Removal of a component from a feature is not supported How can I remove a dynamic

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? 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 be extracted, and at least the .dll must have the expected name. Typically this is easiest to do by adding

I need to add my application to the startup and hence, need to set the Registry Key with the Installation path. I have got this working through the Visual Studio Setup project but can't figure out how to do it through a ClickOnce deployment. Anyone know how to set registry keys when using ClickOnce for installation? codeConcussion ClickOnce can't do this. If you want your app to start when the user logs in, you have to write code in your application to do it (copy a shortcut to the startup folder, edit the registry, etc.) Also, keep in mind that if you write code to handle this scenario, it

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 do not get the same error message if I build the installer through the designer. EDIT: Here is my

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 ReinstallModeText that I changed from omus to amus but that seemed to have no effect. So, how what do

I'm making my own prq file to perform the SQL CE 4.0 installation with my WPF application installation. The installer keeps failing, and I'm not sure why. It looks like it attempts to run the CE exe, but then a Windows Installer help window comes up with all of these command line help options. I click OK, and then it says the installation of CE has failed. I don't how to determine what is going wrong. Here's my prq file contents: <?xml version="1.0" encoding="UTF-8"?> <SetupPrereq> <conditions> <condition Type="32" Comparison="2" Path="HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server