Shortcut properties
I need to create few Entries (like Productname, version, vendorname and Target exe path) in shortcut properties->Details.
Do you have any idea on this?
Kindly help me.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
AngelD
12 years ago
You can't set internal names such as Productname, version, vendorname in a shortcut, they are added in executable files
Changing the target of a shortcut can easily be done with a vbscript:
shortcutPath = "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\MyShortcut.lnk"
targetPath = "C:\Program Files (x86)\MyFolder\MyFile.exe"
Set oWshShell = CreateObject("WScript.Shell")
Set oShortcut = oWshShell.CreateShortcut(shortcutPath)
oShortcut.TargetPath = targetPath
oShortcut.Save
Changing the target of a shortcut can easily be done with a vbscript:
shortcutPath = "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\MyShortcut.lnk"
targetPath = "C:\Program Files (x86)\MyFolder\MyFile.exe"
Set oWshShell = CreateObject("WScript.Shell")
Set oShortcut = oWshShell.CreateShortcut(shortcutPath)
oShortcut.TargetPath = targetPath
oShortcut.Save
Posted by:
bhagu_krish
12 years ago
Posted by:
anonymous_9363
12 years ago
So, we're talking about shortcuts in Vista/Windows 7, then, as XP doesn't have a 'Details' tab.
Either way, the information presented is hard-coded in Explorer. If your client wants additional information, it will either have to go into the 'Description' or he'll need to stump up for you to develop a sub-classing DLL which intercepts the call from Explorer to (I think) SHELL32.DLL and then either shoe-horns in the additional information or presents a new dialog box.
I don't need to fish out the AppDeploy Crystal Ball to know that your client isn't going to stump up the dollars for that.
Either way, the information presented is hard-coded in Explorer. If your client wants additional information, it will either have to go into the 'Description' or he'll need to stump up for you to develop a sub-classing DLL which intercepts the call from Explorer to (I think) SHELL32.DLL and then either shoe-horns in the additional information or presents a new dialog box.
I don't need to fish out the AppDeploy Crystal Ball to know that your client isn't going to stump up the dollars for that.
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.