Shortcut self-healing
Hi,
I'm creating an upgrade app. It's a per-user to per-machine upgrade. Shortcut heals after first launch only. Both the apps only have files going to C:\apps\abc\123 and C:\apps\abc\567. And one shortcut pointing to a file in C:\apps\abc\123\a.bat C:\apps\abc\567\a.bat. There are no registries or files installing to user profile. Eventvwr log points to the batch file launching the shortcut. Both the file and the shortcut are correctly installed.
I took a snapshot of the shortcut launch. It shows only junk.
Please advise.
Regards,
Upkar
I'm creating an upgrade app. It's a per-user to per-machine upgrade. Shortcut heals after first launch only. Both the apps only have files going to C:\apps\abc\123 and C:\apps\abc\567. And one shortcut pointing to a file in C:\apps\abc\123\a.bat C:\apps\abc\567\a.bat. There are no registries or files installing to user profile. Eventvwr log points to the batch file launching the shortcut. Both the file and the shortcut are correctly installed.
I took a snapshot of the shortcut launch. It shows only junk.
Please advise.
Regards,
Upkar
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
That's not what I'd call an upgrade, certainly not in terms of what Windows Installer regards as an upgrade.
Me, I'd set the new version to uninstall the old, making sure that the RemoveExistingProducts action appears nice and early in the sequence, certainly before InstallFiles!
Me, I'd set the new version to uninstall the old, making sure that the RemoveExistingProducts action appears nice and early in the sequence, certainly before InstallFiles!
Posted by:
upkaar
13 years ago
I've already done that. REP is up and before InstallFiles seq. But the shortcut still heals on first launch.
Posted by:
turbokitty
13 years ago
I'm fuzzy on what you're trying to do here. Are you concerned that it's healing on first launch? Check the application event log and it will tell you which component is repairing.
Posted by:
upkaar
13 years ago
I've already done that. Eventvwr log points to the component that installs the batch file launching the shortcut. Both the file and the shortcut are correctly installed.
Posted by:
anonymous_9363
13 years ago
How much time could we have saved if that information had been divulged at the outset?
What actual repair takes place, in terms of file or registry replacement? Does the component contain only that batch file?
What actual repair takes place, in terms of file or registry replacement? Does the component contain only that batch file?
Posted by:
upkaar
13 years ago
[font="trebuchet ms"]How much time could we have saved if that information had been divulged at the outset?
What actual repair takes place, in terms of file or registry replacement? Does the component contain only that batch file?
[font="trebuchet ms"]
[font="trebuchet ms"]All your questions have been answered in my initial query :
[font="trebuchet ms"]
Hi,
I'm creating an upgrade app. It's a per-user to per-machine upgrade. Shortcut heals after first launch only. Both the apps only have files going to C:\apps\abc\123 and C:\apps\abc\567. And one shortcut pointing to a file in C:\apps\abc\123\a.bat C:\apps\abc\567\a.bat. There are no registries or files installing to user profile. Eventvwr log points to the batch file launching the shortcut. Both the file and the shortcut are correctly installed.
I took a snapshot of the shortcut launch. It shows only junk.
Please advise.
Regards,
Upkar
[font="trebuchet ms"]
What actual repair takes place, in terms of file or registry replacement? Does the component contain only that batch file?
[font="trebuchet ms"]
[font="trebuchet ms"]
[font="trebuchet ms"]
I'm creating an upgrade app. It's a per-user to per-machine upgrade. Shortcut heals after first launch only. Both the apps only have files going to C:\apps\abc\123 and C:\apps\abc\567. And one shortcut pointing to a file in C:\apps\abc\123\a.bat C:\apps\abc\567\a.bat. There are no registries or files installing to user profile. Eventvwr log points to the batch file launching the shortcut. Both the file and the shortcut are correctly installed.
I took a snapshot of the shortcut launch. It shows only junk.
Please advise.
Regards,
Upkar
[font="trebuchet ms"]
Posted by:
turbokitty
13 years ago
You really couldn't have worded that any more poorly though. You seem to know which component is the problem. Look inside the component. The MSI isn't healing for the fun of it, there must be a key path.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.