File Extensions
I am new to App-v.. I need clarification in File Extensions..
why file extensions are required in shortcut while sequencing.
How we place file extensions if we creating new shortcut in sequencing time.
why file extensions are required in shortcut while sequencing.
How we place file extensions if we creating new shortcut in sequencing time.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
ksaunam
13 years ago
Posted by:
muni2pop
13 years ago
Hi Kalle,
I done BMC Remedy package, while capturing in App-v after installation part we need to add\edit\delete the shortcut as per the requirement, in that one shortcut doesn't pointing to any location(StartMenu\Desktop) but it has some File associations related to the application and another two shortcuts doesn't have any fileassociations and pointing to StartMenu.. So, to support for other two shortcuts, I supposed to keep the shortcut which contains File associations\File extensions. I mean in all scenarios, this case(Necessity of File associations for shortcut) happens??
I done BMC Remedy package, while capturing in App-v after installation part we need to add\edit\delete the shortcut as per the requirement, in that one shortcut doesn't pointing to any location(StartMenu\Desktop) but it has some File associations related to the application and another two shortcuts doesn't have any fileassociations and pointing to StartMenu.. So, to support for other two shortcuts, I supposed to keep the shortcut which contains File associations\File extensions. I mean in all scenarios, this case(Necessity of File associations for shortcut) happens??
Posted by:
ksaunam
13 years ago
Yeah, sometimes applications in Sequencer's application list get assigned file associations and have no visible entry points (shortcuts) for them. This usually indicates that the application handles its file associations through some launcher executable which is never meant to be started directly by the end user.
If you customize your published apps, I would suggest leaving those ones intact as you just cannot arbitrarily change file associations to another executable without knowing if app supports it.
Is this what you were asking of?
If you customize your published apps, I would suggest leaving those ones intact as you just cannot arbitrarily change file associations to another executable without knowing if app supports it.
Is this what you were asking of?
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.