Refer to the following link: http://forum.installsite.net/index.php?showtopic=20475&hl= I hope that helps. I posted that for removing "Installshield" from the bottom of the dialogs for both Basic MSI and Installscript project types. The approaches are entirely different owing to the difference in the installation methodologies and engines. I hope that was what you were asking. ... View more

What project type are you working on? Could you please explain the deletion part of your problem? Where are you deleting the files from? And what problem you had in deleting dynamic links? ... View more

When you create a minor upgrade package, it is in effect a new package. The package GUID will have to be different. But the Product GUID remains same. Also, the upgrade GUID is untouched. Now the full details are: You create a package for Version 1.0.0 of application ABC.It has a package GUID, say,{21EC2020-3AEA-1069-A2DD-08002B30309D}. Clients install it on their machines. The msi is cached on the system in a hidden folder Windows\Installer. If clients run the same package again, repair or maintenance of the installed software is triggered. The identity of the package is the GUID. Windows Installer checks for the GUID and the cached package in the hidden folder. Now you package a minor upgrade of your app ABC. Its version is 1.1.0. The package must have a different GUID to distinguish it from a package meant for version 1.0.0. Otherwise the maintenance install of version 1.0.0 will be triggered when 1.1.0 package is being invoked. Once the patching is done the the 1.0.0 version is transformed to 1.1.0 and the package GUID is also updated. Patching turns version 1.0.0 to 1.1.0. Invoking a 1.1.0 package on this machine will now trigger the repair. Taking the above example forward, 1.0.0 version msi file was cached on the system. The patch for version 1.1.0 contains transforms that are applied to the 1.0.0 msi file at run time. This is the first step performed by the Windows Installer engine. The installation now proceeds in the repair or maintenance mode. This is because Patching is considered to be a repair. But the msi being used in the repair will be 1.1.0. Reinstallation of the product happens according the REINSTALLMODE parameters passed. This transformation of the 1.0.0 msi to 1.1.0 msi persists in case of non-uninstallable patches. The only way to remove the patch is to uninstall the application and install the base version. As a setup developer, one need not worry about things cluttering up in the system. Windows Installer is smart enough to keep only the required info. There are other important things like uninstallable and non-uninstallable patches. Also got through these: http://blogs.msdn.com/b/heaths/archive/2005/09/12/464047.aspx http://msdn.microsoft.com/en-us/library/aa371182(v=vs.85).aspx ... View more

As wollka said there is a limit. Go through these: http://kb.flexerasoftware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q200878&sliceId= http://helpnet.flexerasoftware.com/robo/projects/installshield16verification/errorhelp.htm ... View more

You should configure your install for the Upgrade and Downgrade scenarios. That is the only way to make your installation detect old or new versions. Now why is package GUID important? It is because when you install an app for the first time, the msi database is cached on the local system. Be aware that Windows Installer engine, when invoked, always checks for the package guid in the registry. So, when you run the install for the second time, it checks the registry and finds the GUID and launches a repair. In case you change the GUID, and do not configure your package for upgrade and downgrade scenario, your package is simply installed. Go through these: http://kb.flexerasoftware.com/doc/Helpnet/installshield14helplib/PreventingDowngrades.htm http://msdn.microsoft.com/en-us/library/aa372379(v=vs.85).aspx The Upgrade Table can be configured in Direct Editor if you are advanced enough or you can use the Upgrades view UI . ... View more

Did you try all the three options? Even the one where you pass ""(empty string) as the first parameter? Also, check the existence of the said file before calling LaunchAppandWait. ... View more

Could you throw more light on the steps you followed to create the dialog? How did you insert it into the standard sequence? ... View more

Questions: a) Are you calling any other .NET assembly prior to this call to CoCreateObjectDotNet()? If yes, what .NET version does that depend on? b) Are you calling the same .NET assembly prior to this particular call? c) As you are calling this dll from INSTALLDIR, I assume that you are installing it into the system. Are you calling it at the right point in the execution sequence? d) The file has to be present on the system for the call to be successful. So have you sequenced your CA after InstallFinalize or such actions? Provide the answers to these queries. Also, perform the following steps if you feel you are doing the other things right: vcredist installation was suggested in desperation. But I would suggest you open ProcMon.exe and look at the version of .NET being used by the installer. A mismatch in the version being used at run time can be the issue. Run ProcMon.exe first on a machine where your installation succeeds. Note the version of .NET being used. Then repeat the step on the machine where it fails. You know what version your assembly was compiled in? Even if you do not know, Procmon.exe readings on the machine where your installation succeeds will tell you the correct version of .NET needed. ... View more

What is the class name? If it is tAuthority, try using just that tAuthority in the parameter rather than using ABC.tAuthority. ... View more

Try installing vcredist 2005 or 2008 or 2010(according to the VS installed on successful machines) on any of the machines where it fails and try the install. Any of them, if missing, will cause issues. NOTE: vcredist 2010 will not be enough for apps that need vcredist 2008 or 2005. So installing vcredist 2010 will be of no use. You have to install vcredist 2005 for apps that need it even if your machine has vcredist 2010 already installed. ... View more

Try using DotNetCoCreateObject instead of the one you are using and let me know. ... View more

Has it got the COM VISIBLE attribute set? ... View more

Did you create the dll? ... View more

Try using LaunchAppAndWait i the following manner: LaunchAppAndWait ( szProgram, szCmdLine, nOptions ); where szProgram = "" szCmdLine = path to the Commandfile.cmd file nOptions = your options. ------------------------------------------------------ also try this szProgram = path to cmd.exe szCmdLine = path to the Commandfile.cmd file nOptions = your options. ------------------------------------------------------ also try this szProgram = "cmd.exe" szCmdLine = path to the Commandfile.cmd file nOptions = your options. Also look at ChangeDirectory(). This is an Installscript function. You can use this in place of LAAW_OPTION_CHANGEDIRECTORY if the above options do not work. Hope this helps... ... View more

You can always use Win APIs. Either a C++ dll Custom Action(CA) or Installscript CA that uses Kernel32.dll can be employed. Go through this: http://msdn.microsoft.com/en-us/library/ms684834(v=vs.85).aspx ... View more