Thanks! --Greg ... View more

I discovered Install Shield is crashing when it tries to do .NET dependency scanning and I was able to work around the problem by turning that feature off during build -- set the "Organization -> Components -> .NET Settings -> .NET Scan at Build" option to None. --Greg ... View more

I'm also running into the same error. --Greg ... View more

I've done some more testing, and it appears once I've tried to do an upgrade using an installer that broke the "minor upgrade" rule of removing a component, the machine appears to get corrupted, such that no future upgrades/installs (either minor upgrade or major upgrade) seem to work right on that machine for that application that uses the same upgrade code -- even when I completly uninstall the application, and then try installing the application again. However, if I wipe the machine and reinstall the operating system, and then test upgrade/installs (including both testing minor upgrade and major upgrade) work fine (as long as all my installers do a major upgrade when a component is removed, otherwise do a minor upgrade if only file versions changed). I was wondering, is there any way to clean out all the entries (component guids, product guids, etc.) related to a given upgrade code (e.g. to "uncorrupt" the machine), rather than having to reinstall the operating system to clear it out the problem? Where are those entries being stored on the machine (e.g. in the registry, in a database file somewhere)? Thanks, Greg ... View more

Looks like the VM I was testing on got corrupted from my earlier installation testing. I created a new clean VM and tested again, and the upgrade and unistall went fine as I expected using the major upgrade. ... View more

I don't have that many files; I am starting to become tempted to just create a custom action to copy or remove the files rather than let MSI manage them via components and features. ... View more

I discovered it seems I need to add a row to the MSI Upgrade table for the major upgrade. I did this in the Install Shield UI by going to the Installation Designer tab, Media -> Upgrades, right clicked on Prepare Setup For Upgrade Scenarios -> Upgrade Windows Installer Setup, and choose "Add Major Upgrade Item". In the Common tab, in the "Major Upgrade settings", I selected "Completely uninstall old setup before installing new setup". I clicked on the new "major upgrade" item that got inserted, on that Common tab, in the Major Upgrade group, I choose "products sharing my Upgrade Code" for the target product family, and in the Product Version group, choose "Any earlier version.". The installer now is upgrading as I expected. It is correctly upgrading the files that still exist from the previous version and removing the files from the previous version that no longer exist in the new version. However, I've run into a new problem. When I choose to uninstall, it is not removing the files that exist in the new version and also existed in the previous version. It does remove the files that were added in the new version but didn't exist in the previous version. In the MSI debug log from the uninstall, for the files its not removing that I would have expected it to remove I see entries that look like this: MSI (s) (8C:7C) [15:34:35:008]: Executing op: AssemblyPublish(Feature=***************,Component={953E6F53-0CA1-4C08-81D2-21E0860A5B76}[~]2,AssemblyType=3,AppCtx=C:\Program Files\***********\*********\*************.exe,AssemblyName=**************,Version="1.1.0.3",PublicKeyToken="B2BDF9846F079B4F",Culture="neutral",FileVersion="1.1.0.3",ProcessorArchitecture="MSIL",) MsiPublishAssemblies: Application Context:C:|Program Files|**********|************|**********.exe, Assembly Name:*************,Version="1.1.0.3",PublicKeyToken="B2BDF9846F079B4F",Culture="neutral",FileVersion="1.1.0.3",ProcessorArchitecture="MSIL" MSI (s) (8C:7C) [15:34:35:008]: Note: 1: 1402 2: UNKNOWN\Installer\Assemblies\C:|Program Files|************|*************|**************.exe 3: 2 I noticed its refering to version "1.1.0.3", but I would have expected that version to all be gone from the "major upgrade" that I installed which brought the files to version "2.2.2.2". Any ideas why this is happening? Or what I can do to make it such that it uninstalls all the files? Thanks, Greg ... View more