Jayzen
12-17-2002, 04:19 PM
This is a wierd one. I have 3 versions of my program, the original version (2.20), the patched version (2.35) and the latest version (2.38).
I used the patch design view in the IDE to make a patch that can go from either 2.20 or 2.35 to 2.38. Amazingly the patch works great, all files are correctly patched.
The only problem is that when the patch is installed, all the shortcuts created for the original install get copied out to the root of the Program Menu. Not moved, just copied. So there are 2 copies of each shortcut, one in the original folder (where they are supposed to be) and one in the root of the Program Menu.
When uninstalling, the copies in the root don't get removed.
The only thing that I'm doing "wierd" with shortcuts is I use the SHELL_OBJECT_FOLDER variable when creating the path to the shortcuts so the user can put the shortcuts anywhere he wants. I made a quickpatch from 2.20 to 2.35 and it didn't do this.
Anyone seen this, know how to fix it, or know what I can do to prevent it?
If all else fails, is there a way to run installscript after a patch? Maybe I could just go in and erase them after the patch is done. Of course I'd rather fix this the right way but I need to ship this patch within the next few days.
I used the patch design view in the IDE to make a patch that can go from either 2.20 or 2.35 to 2.38. Amazingly the patch works great, all files are correctly patched.
The only problem is that when the patch is installed, all the shortcuts created for the original install get copied out to the root of the Program Menu. Not moved, just copied. So there are 2 copies of each shortcut, one in the original folder (where they are supposed to be) and one in the root of the Program Menu.
When uninstalling, the copies in the root don't get removed.
The only thing that I'm doing "wierd" with shortcuts is I use the SHELL_OBJECT_FOLDER variable when creating the path to the shortcuts so the user can put the shortcuts anywhere he wants. I made a quickpatch from 2.20 to 2.35 and it didn't do this.
Anyone seen this, know how to fix it, or know what I can do to prevent it?
If all else fails, is there a way to run installscript after a patch? Maybe I could just go in and erase them after the patch is done. Of course I'd rather fix this the right way but I need to ship this patch within the next few days.