The Community is now in read-only mode to prepare for the launch of the new Flexera Community. During this time, you will be unable to register, log in, or access customer resources. Click
here
for more information.
I'd move that shortcut out of the ShortcutComponent into the component where the target file is. Make that file key file and you can even advertise this shortcut.There's no need for those registry entries as long as the shortcut goes into ProgramMenu...
Hi there,So you want to capture the uninstaller.Well, you'll need to change the options to check for deleted files and registry entries to capture an uninstall when running the repackaging wizard.You could monitor this one if you have an uninstall.ex...
I don't think that MSI can cope with changes to component destinations on a per user basis. Have a look at the restrictions in the MSI helphttp://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/changing_the_target_location_for_a_d...
The current user component should be able to use the registry entries from the cached MSI without asking for the source. Usually a missing file causes Windows Installer to go back to the source (check out the event viewer).Have a look at property SOU...
hi,just to confirm, the .net framework is separate indeed.well , you could put it in the binary table and kick it off via a custom action, but i wouldn't recommend that.however, the .net framework is only required if you are installing a .net softwar...
