Today, a colleague asked me a question. After installing the program using the program installation package provided by me, I found that the created application shortcut property form contains a [start position (s ):] There is a problem with the file path. I will check it according to the view method he said. No, the [target (t):] item path is "C: /program files/product name/product .exe ", but the path of the [start position (s):] item is" C:/program files/product name/log ". Ah, how did this happen? As a result, I began to think about whether the registry information was read properly or not. I found no prompts in the Registry for a long time. Open the installation script, find the location where the shortcut script is created, and find a problem. The path in [starting position (s):] is "C:/program ".
Files/product name/log is the script used to create a shortcut script. This seems to have prompted me something. I tried to move the script for creating a shortcut to "$ instdir/product name" and re-compile the script to solve the problem.
[Target (t):] the path of the item is "C:/program files/product name/product .exe ";
[Start position (s):] The item path is "C:/program files/product name"
Example:
Setoutpath "$ instdir/product name"
File "product .exe"
Createshortcut "$ desktop/product. lnk" "$ instdir/product name/product .exe"
Script order should be arranged.
In some applications, the shortcut [start position (s):] item created is null. I have not carefully studied how to implement it. If anyone knows, please advise.
The above content may be omitted. the viewer may criticize and give advice.