Delete the existing shortcut in entirety. Create the new desired one during minor upgrade. You can use DeleteFolderIcon and AddFolderIcon Installscript functions wrapped in a Custom Action to easily do the job. You may also use Win32 APIs, if you are comfortable with them. ... View more

This happens when some component that Windows Installer installed gets corrupted. Allow Windows Installer to repair the application and see if the issue gets resolved. You can then view the log and see what was actually repaired. The log file can be found in some random directory in %temp%. One of the basic reasons for having Windows Installer as a SERVICE is that it can constantly monitor the health of apps it installed. ... View more

Please read the basics of setup development and deployment before posting. Also, what do you expect as outcome in the scenario you have mentioned. ... View more

Firstly: What type of files are they?(versioned, unversioned etc...) Secondly: Check the uninstall log for the reason for the files not getting deleted. There is no reason for a developer to handle the removal of files during uninstall. This is the installer's job. Go through the log thoroughly first. ... View more

You do not have to define those GUIDs. They are automatically added when you create a Feature in the Installshield IDE. You can change those GUIDs later, though. You have to look int the ORGANIZATION-->FEATURES. Click on the feature you want and you can find its GUID listed on the right side GRID. ... View more

You need to use the Feature GUID for the query. ... View more

Features in registry would be represented using GUIDs. You can also check the install log. That has all the info in one place. ... View more

The complete uninstall and subsequent install Major Upgrade will have no problems. You have to use the RemoveFile table as jenskjensen mentions althugh not for the reasons he mentions. That is the proper and the easiest way out of this trouble. Go through this: http://msdn.microsoft.com/en-us/library/windows/desktop/aa371201(v=vs.85).aspx Post if you need more info. ... View more

What type of upgrade did you configure? Also, as you say there is no key file for the component, the folder itself becomes the keyfile or keypath to be precise. Removal of non-key files from a component that has no keyfile will not be that straightforward. ... View more

It would be a nightmare at best. And I do not understand why you need to perform such a check. Give more details if possible. WMI Remote Registry etc... come to my mind. These need to be enabled on remote PC. But all this needs a mutual understanding between machines and OSs on them. Also, opening up of such channels of communication would be a security challenge as well. ... View more

Try looking into the log. And post relevant details. ... View more

Glad that you figured it out. ADDENDUM: I am quoting myself from earlier posts in the same thread: Ok, so apparently Flexera Software is supplying an OLD version of the Prerequisite file for "Visual C++ 2005 SP1 Redistributable Package (x86)". The version they point to and supply is for 8.0.50727.762, a newer version was released after that version with an ATL Security update, Version 8.0.50727.4053 This is a classic WinSxS issue. I asked you, repeatedly, to install various versions of vcredist.exe for the same reason. Further, Dependency Walker can also show you the path form where it is trying to fetch ATL80.dll & MSVCR80.dll from. This can give you the exact answer to what version of ATL80.dll & MSVCR80.dll is needed. It would be a path that contains WinSxS. That can further guide you in selecting the vcredist version. This is what I said about finding the versions. ONe should always perform these steps prior to anything else when side-by-side assemblies are involved. This step would have nailed the problem in its infancy and saved you time. KEYWORDS for further search: Side-by-side install Side-by-side assemblies WinSxS manifests local manifests isolated application... It is a wonderful concept that MS has introduced: WinSxS. But little knowledge exists about this in the developer community. ... View more

My installation routine will not ever be run in silent mode. Question is...how? Running the MSI in the installer is exactly what I want to do, but I need to know how. It is all about invoking the CR-SAP MSI file in the UI Sequence of your install. You can use the Installscript's venerable LaunchAppAndWait function. Call msiexec.exe using LaunchAppAndWait. Look into Installshield help for details and examples. I am not familier with creating a Bootstrapper.exe.... Is that a single self contained, self extracting file like regular setup exe's? Is there a utility to create one? A simple Win32 console application exe that uses Win32 API's CreateProcess() function and: 1) Launches the CR-SAP MSI file by passing it as an argument to msiexec.exe and waits for the execution to finish 2) When the above process returns, invokes your setup.exe and exits. I havn't gone through this type of test yet. Although I honestly do not believe it will help, If I can't come up with an answer using the methods above, then this will be my next step. This is the easiest of all. You should do this first. Something like: 1)Install the plain vcredist.exe and install your app. Test it. If the above works stop and include the vcredist in your setup. Else 2)Install the vcredist.exe SP1. Test your app. You do not need to installl your app as its already installed as part of STEP 1. So on... vcredist.exe can be run manually during the test phase. ... View more

Further, Dependency Walker can also show you the path form where it is trying to fetch ATL80.dll & MSVCR80.dll from. This can give you the exact answer to what version of ATL80.dll & MSVCR80.dll is needed. It would be a path that contains WinSxS. That can further guide you in selecting the vcredist version. ... View more

1) Is there a way that I can incorprate the supplied MSI for the CR-SAP dependancy files into my Installation Project, so that it runs the MSI first? Kinda like a prerequisite file? Sure. Run the CR-SAP MSI in the UI Sequence of your installer. The only downside of this approach will manifest itself whent he user goes for a silent install, in which case, the CR-SAP MSI will not be executed. You cannot sequence it anywhere else. So, do this if its guaranteed that the user will not run it in silent mode. OR Create a bootstrapper exe that invokes CR-SAP MSI first, waits for it to finish and then invokes your installer. This is the better of the two approaches. I ran a utility called "Depends.exe" and found that the follwing two DLL files that CR-SAP requires are missing, ATL80.dll & MSVCR80.dll. Can you run all flavors of vcredist 2005(plain, sp1 ...)available one by one and test your app. Install vcredist manually and do not include it in your setup for testing. ... View more