Shortcut table question
in my shortcut table, I have a few items i'm not clear about.
The first is the 'Target' field. This particular target value is, "[#Myapp.exe] and the Shortcut Field is populated with, "MYAPP.EXE1".
The one I'm more concerned with is the Target value. I'd like to know what the "#" is for. Then, why does the shortcut name have the "1" at the end?
Thanks for your help!
The first is the 'Target' field. This particular target value is, "[#Myapp.exe] and the Shortcut Field is populated with, "MYAPP.EXE1".
The one I'm more concerned with is the Target value. I'd like to know what the "#" is for. Then, why does the shortcut name have the "1" at the end?
Thanks for your help!
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
AngelD
17 years ago
If the Target column had pointed to Myapp.exe this would be a component but as the column has the value of [#Myapp.exe] it is referring to a file with the long path, [!Myapp.exe] would be the short path (DOS 8.3). If the Target column/field has a component value the shortcut will be advertised and if it points to a property or file as in this case it will be a regular shortcut.
Regarding the Shortcut field:
Let say that you have a desktop and a startmenu shortcut pointing to MYAPP.EXE, if the desktop shortcut was first added the Shortcut field for this shortcut would be MYAPP.EXE and for the next shortcut (startmenu) MYAPP.EXE1. Having another shortcut pointing to the same exe would add 1 to the end again making this primary key (Shortcut field) MYAPP.EXE2.
Regarding the Shortcut field:
Let say that you have a desktop and a startmenu shortcut pointing to MYAPP.EXE, if the desktop shortcut was first added the Shortcut field for this shortcut would be MYAPP.EXE and for the next shortcut (startmenu) MYAPP.EXE1. Having another shortcut pointing to the same exe would add 1 to the end again making this primary key (Shortcut field) MYAPP.EXE2.
Posted by:
rpfenninger
17 years ago
Don't be concerned. All seems to be fine from my view.
The # stands for the component Myapp.exe (not the file!). Because this is an advertised shortcut which will lead to the component, not directly to the file.
The 1 at the end of the file, I assume this is because that file with the same name is more than ones in your package. That's why the first one is called MyApp.exe, then MyApp.exe1, MyApp.exe2 etc.
Check your file table. I'm sure you'll find it.
Hope this helps
Cheers
Roland
The # stands for the component Myapp.exe (not the file!). Because this is an advertised shortcut which will lead to the component, not directly to the file.
The 1 at the end of the file, I assume this is because that file with the same name is more than ones in your package. That's why the first one is called MyApp.exe, then MyApp.exe1, MyApp.exe2 etc.
Check your file table. I'm sure you'll find it.
Hope this helps
Cheers
Roland
Posted by:
Secondlaw
17 years ago
I initially thought the '#' was referring to the component but I had to ask the question because there is also a 'component' field which points to a completely different component. So which one will it use? Isn't it odd that it would point to two seperate components? Sorry, I just don't understand why it's set up like this and am trying to get a better understanding.
Thanks for your answers!
Thanks for your answers!
Posted by:
Secondlaw
17 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.