As far as I know when registry entry HKLM \SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{MY_PRODUCT_CODE}\WindowsInstaller exists and is set to "1", then "UninstallString" entry is ignored and MsiExec.exe /x{MY_PRODUCT_CODE} is used instead. Recommended way to change “Add/Remove Programs” behavior is to set ARPSYSTEMCOMPONENT property to 1 and manually create a set of custom uninstall registry values under your own uninstall key from your msi (for example HKLM \SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ ). ... View more

Superfreak3 wrote: After marking to install locallay from the Feature Selection dialog, the files are installed. I did not expect this. You made manual command to install the feature, but expected the command to be ignored? Sounds weird. Inadvertent run through the maintenance install is just clicking Next, Next, Next (IMHO). That scenario won’t install the feature. ... View more

Windows Installer does not allow targeting 64-bit Program Files from 32-bit msi packages. It’s possible to install to both Program Files and Program Files(x86) from 64-bit msi package. But 64-bit msi can’t be used to install on 32-bit OSes. So you might need to build two msi packages – 32 and 64 bit. ... View more

When we faced this issue the only way we found suitable for us – launch executable from dll custom action. So de-elavation happens in dll code. Actual trick was written not by me, so I don’t know much. Main idea was to get Shell object and use its ShellExecute method. As I understand it, we launch not from out setup.exe as parent process, but from explorer which is in most cases de-elevated. ... View more

Go to Installation Designer, Behavior and Logic -> Property Manager. Note what value INSTALLLEVEL property has (usually it’s 100). We will need to know that value later. Go to Installation Designer, Organization -> Setup Design. Make sure that: 1) “Required” setting of both features is set to “No”. 2) “Install Level” of both features is higher than INSTALLLEVEL property (for example 200). 3) Condition for 32-bit feature sets Level to 1 (or any other value lower than INSTALLLEVEL) upon condition “Not VersionNT64”. 4) Condition for 64-bit feature sets Level to 1 upon condition “VersionNT64”. 5) 32-bit and 64-bit Components belong to (and only to) corresponding features. All said is for Basic MSI project type. ... View more

There is no need to list already installed features in modify mode. You should get something like: Event __________ Argument _______________ Condition AddLocal ________ FeatureToBeAddedName1 __ CorrespondingPropertyFromSystemSearch1 And (_IsMaintenance = "Change") AddLocal ________ FeatureToBeAddedName2 __ CorrespondingPropertyFromSystemSearch2 And (_IsMaintenance = "Change") ... View more

One of my projects is similar to the one that you described. By default features which were not installed by fresh install are deselected, but they can be set to Install state on CustomSetup dialog and Modify mode actually works for me (installs new features). If you want feature state to be changed without manual actions on CustomSetup dialog, you can use “AddLocal” event on (for example) Next button of MaintenanceType dialog when modify option is chosen and System Search has found third party app. BTW, I’m talking about basic MSI project. ... View more

First that came to my mind – check if in your project IS_SQLSERVER_SERVER property is listed in SecureCustomProperties. It should be. That will ensure that value set in UI sequence will be transferred to execute sequence too. Also I would search msi log to find out when IS_SQLSERVER_SERVER property changes its value. Usually it helps to understand why. ... View more

I would try going to “Files and Folders” view, right click on “Destination Computer”, and in “Show Predefined Folders” menu choose [ProgramFiles64Folder]. ... View more

To avoid such issue I added custom action that checks if user is admin and if not sets special property (let’s call it USER_NON_ADMIN). Then I added Error Custom Action with condition USER_NON_ADMIN which asks user to log on as an administrator and retry the installation. ... View more

Same problem is being discussed in this topic: http://social.msdn.microsoft.com/Forums/en-US/winformssetup/thread/09f72e05-f43f-4e7e-81b6-f81c1b60dc6c For me next entry was useful: It appears that repro machines that have a desktop.ini with read-only attribute set on it results in the message on uninstall appearing. If the read-only attribute is removed the message wont appear. For a per-machine installed package the desktop.ini of interest would be located here: :\Users\Public\Public Desktop\. I added Custom Action that removes read-only attribute from public desktop.ini before uninstallation. I'm not sure if it's the best solution, but it works. ... View more

Forgot to specify – my experience was with Basic MSI projects which are stored as XML. ... View more

What you want is doable. The only trouble I had – TFS Auto Merge “spoils” ISString table in the ism. To avoid this I always choose to Merge Changes In Merge Tool (tick “Navigate conflicts only”, in most cases there is no conflicts). ... View more

As possible solution to problem with services – add property MSIRESTARTMANAGERCONTROL with value Disable to your project. Or: http://buildmaestro.wordpress.com/2011/03/14/suppress-filesinuse-dialog-on-uninstall/ ... View more

The only thing I can think of: check Directory table in the Direct Editor – is there any difference between BIN1 and FIXSTORE folders in Directory_Parent column? ... View more