Shortcut Working directory problem
Hi All,
I have come across a problem when the working directory of a Shortcut is set to the USERPROFILE (or another user sepcific location).
If the installation is for a machine with multiple users it will cause issues.
User1 installs - fine
User2 logs in - repairs - fine
User1 logs back in - no repair, and working dir is set to User2 profile.
Our solution was to manually change the shortcut work dir to %USERPROFILE% and include the shortcut as a file (.lnk) in the file table. This seems to work but we then do not have an advertised shortcut.
btw - %USERPROFILE% doesn't work in shortcut table.
Any ideas or comments on this??? Please???
Cheers,
Aidy.
I have come across a problem when the working directory of a Shortcut is set to the USERPROFILE (or another user sepcific location).
If the installation is for a machine with multiple users it will cause issues.
User1 installs - fine
User2 logs in - repairs - fine
User1 logs back in - no repair, and working dir is set to User2 profile.
Our solution was to manually change the shortcut work dir to %USERPROFILE% and include the shortcut as a file (.lnk) in the file table. This seems to work but we then do not have an advertised shortcut.
btw - %USERPROFILE% doesn't work in shortcut table.
Any ideas or comments on this??? Please???
Cheers,
Aidy.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
MSIPackager
18 years ago
Our solution was to manually change the shortcut work dir to %USERPROFILE% and include the shortcut as a file (.lnk) in the file table. This seems to work but we then do not have an advertised shortcut.
Why can't you have this as your advertised shortcut? As long as this entry in the file table is the keypath for the component used your shortcut table it should advertise OK - shouldn't it?!
Cheers,
Rob.
Posted by:
brenthunter2005
18 years ago
Posted by:
islander222
18 years ago
Hi MSIPackager,
The entry in the file table will be the .lnk file, We won't have any entry in the shortcut table - Maybe I'm missing something here??
Hi brenthunter2005,
I have tried that but it will only resolve at install time or repair time. Not when the original user logs back in after another user.
The entry in the file table will be the .lnk file, We won't have any entry in the shortcut table - Maybe I'm missing something here??
Hi brenthunter2005,
I have tried that but it will only resolve at install time or repair time. Not when the original user logs back in after another user.
Posted by:
brenthunter2005
18 years ago
Posted by:
islander222
18 years ago
I'm not sure on that one - actually I'm not 100% clear on exactly what the working dir does to be honest.
But in this case run time files are created for each user when they run the shortcut (In the work dir location).
The customer wants these files retained as per the applications normal functionality.
But in this case run time files are created for each user when they run the shortcut (In the work dir location).
The customer wants these files retained as per the applications normal functionality.
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.