I'm doing something similar to this for a NSIS installer that allows
me to deploy my webapp to the local machine.
So when my installer is creating the shortcut to prism it writes the
following for the executable link in the shortcut:
"$INSTDIR\prism\prism.exe" "-profile $\"$INSTDIR\Prism.profile$\" -
override $\"$INSTDIR\WebApps\
alts-we...@prism.app\override.ini$\"
-webapp $\"$INSTDIR\WebApps\
alts-we...@prism.app$\"
Lets say that the installation directory is C:\MyApp... this then
becomes:
"C:\MyApp\prism\prism.exe" -profile "C:\MyApp\Prism.profile" -
override"C:\MyApp\WebApps\
my...@prism.app\override.ini" -webapp "C:
\MyApp\WebApps\
my...@prism.app"
Note that I've included a Prism profile directory along with my
application and am explicitly referencing it in the command line.
I haven't looked into Portable apps much... but I'd guess that you
want the links to the portable app to be relative to the short cut
location so they don't have to specify drive letters otherwise the app
wouldn't work if it got a different drive letter than expected. So
you'd need to layout the portable drive like so:
\ (Root of device)
Shortcut to MyApp
Shortcut to Firefox
\Portable MyApp
\Portable MyApp\prism
\Portable MyApp\Prism.profile
\Portable MyApp\WebApps/
my...@prism.app
\Portable Firefox
...
And the shortcut executable path would look like:
"Portable MyApp\prism\prism.exe" -profile "Portable MyApp
\Prism.profile" -override"Portable MyApp\WebApps\
my...@prism.app
\override.ini" -webapp "Portable MyApp\WebApps\
my...@prism.app"
Hope that helps,
Ben