EasyManua.ls Logo

VMware THINAPP 4.6 - Configuring Dependent Applications with Application Link; Application Link Pathname Formats

VMware THINAPP 4.6
146 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
VMware, Inc. 91
Chapter 5 Configuring Package Parameters
Examples
IfyouhaveanapplicationonaUSBdrive,youcanmodifytheWorkingDirectoryvaluefromthedefaultUSB
locationtotheMy Documentsdirectoryonthedesktop.
[<app>.exe]
WorkingDirectory=%Personal%
ThelocationoftheMy Documentsdirectorydependsontheisolationmodesetting.Tomaptheworking
directorytotheMy Documentsdirectoryonthephysicalsystem,usetheMergedisolationmodesetting.To
maptheworkingdirectorytothesandboxonthelocalmachine,usetheWriteCopyorFullisolationmode
setting.
Configuring Dependent Applications with Application Link
TheApplicationLinkutilitykeepssharedcomponentsordependentapplicationsinseparatepackages.Inthe
Package.inifile,youcanusetheOptionalAppLinksandRequiredAppLinksentriestodynamically
combineThinApppackagesatruntimeonendusercomputers.Thisprocessenablesyoutopackage,deploy,
andupdatecomponentpiecesseparatelyandkeepthe
benefitsofapplicationvirtualization.
ThinAppcanlinkupto250packagesatatime.Eachpackagecanbeanysize.Thelinksmustpointtothe
primarydatacontainerofapackage.
Sandboxchangesfromlinkedpackagesarenotvisibletothebasepackage.Forexample,youcaninstall
AcrobatReader
asastandalonevirtualpackageandasalinkedpackagetothebaseFirefoxapplication.When
youstartAcrobatReaderasastandaloneapplicationbyrunningthevirtualpackageandyouchangethe
preferences,ThinAppstoresthechangesinthesandboxforAcrobatReader.WhenyoustartFirefox,Firefox
cannotdetect
thosechangesbecauseFirefoxhasitsownsandbox.Openinga.pdffilewithFirefoxdoesnot
reflectthepreferencechangesthatexistinthestandaloneAcrobatReaderapplication.
FormoreinformationabouttheApplicationLinkutility,see“A p p l i c a t i o n LinkUpdates”onpage 56,
“OptionalAppLinks”onpage 93,and“RequiredAppLinks”onpage 92.
Application Link Pathname Formats
TheApplicationLinkutilitysupportsthefollowingpathnameformats:
Pathnamescanberelativetothebaseexecutablefile.Forexample,
RequiredAppLinks=..\SomeDirectoryresultsinC:\MyDir\SomeDirectorywhenyoudeploythe
baseexecutablefiletoc:\MyDir\SubDir\ Dependency.exe.
Pathnamescanbeabsolutepathnames.AnexampleisRequiredAppLinks=C:\SomeDirectory.
PathnamescanuseanetworkshareoraUNCpath.Anexampleis
RequiredAppLinks=\\share\somedir\Dependency.exe.
Pathnamescancontainenvironmentvariablesanddynamicallyexpandtoanyoftheprecedingpath
names.AnexampleisRequiredAppLinks=%MyEnvironmentVariable%\Package.dat.
Theriskofusingenvironmentvariablesisthatausermightchangethevaluesbeforestartingthe
applicationandcreateanApplicationLinkdependencyotherthantheonethattheadministrator
setup.
PathnamescancontainThinAppfoldermacros.Anexampleis
RequiredAppLinks=%SystemSystem%\Package.dat.
Pathnamescanspecifymultiplelinksordependencieswithasemicolonthatseparatesindividual
filenames.AnexampleisRequiredAppLinks=Dependency1.exe; Dependency2.exe;.
Pathnamescancontainasteriskandquerywildcardcharacters(*and?)infilenamesandpathlocations.
Forexample,RequiredAppLinks=WildPath*\WildFilename*.dat.
Ifapathcontainingawildcardcharactermatchesmorethanonedirectoryinthefilesystem,each
matchingdirectorynamewillbereturned,toenableadditionalpathorfilename
matching.

Table of Contents

Related product manuals