VMware, Inc. 59
Chapter 4 Updating and Linking Applications
3CaptureApplicationB.
4InthePackage.inifileforApplicationB,specifyApplicationCas arequiredoroptionalapplicationlink.
Forexample,addRequiredLinks=\AppFolder\AppC\AppC.exetothefile.
5CaptureApplicationC.
IfyoustartApplicationA,itcanaccessthefilesandregistrykeysofApplicationBandApplicationBcan
accessthefiles
andregistrykeysofApplicationC.
Affecting Isolation Modes with Application Link
ThinApploadsanApplicationLinklayerduringapplicationstartupandmergesregistryentriesandfile
systemdirectories.IfThinAppfindsaregistrysubkeyorfilesystemdirectorythatdidnotpreviouslyexistin
themainpackageorlayerthatisalreadymerged,ThinAppusestheisolationmodespecifiedinthelayer
being
loaded.If theregistrysubkeyorfilesystemdirectoryexistsinthemainpackageandalayerthatisalready
merged,ThinAppusesthemostrestrictiveisolationmodespecifiedinanyofthelayersormainpackage.
The orderofmostrestrictivetoleastrestrictiveisolationmodesisFull,WriteCopy,and
Merged.
PermittedGroups Effect on Linked Packages
IfyoulinktwoapplicationsandyouspecifyavalueforthePermittedGroupsparameter,theuseraccount
usedforstartingtheapplicationmustbeamemberofatleastoneoftheActiveDirectorygroupsforthis
parameterinthePackage.inifilesofbothapplications.ForinformationaboutthePermittedGroups
parameter,
see“ConfiguringPermissions”onpage 72.
Sandbox Changes for Standalone and Linked Packages
Sandboxchangesfromlinkedpackagesarenotvisibletothebaseexecutablefile.Forexample,youcaninstall
AcrobatReaderasastandalonevirtualpackageandasalinkedpackagetothebaseFirefoxapplication.When
youstartAcrobatReaderasastandaloneapplicationbyrunningthevirtualpackageandyou
changethe
preferences,ThinAppstoresthechangesinthesandboxforAcrobatReader.WhenyoustartFirefox,Firefox
cannotdetectthosechangesbecauseFirefoxhasitsownsandbox.Openinga.pdffilewithFirefoxdoesnot
reflectthepreferencechangesthatexistinthestandaloneAcrobatReaderapplication.
Import Order for Linked Packages
ThinAppimportslinkedapplicationsaccordingtotheorderofapplicationsintheRequiredAppLinksor
OptionalAppLinksparameter.Ifeitherparameterspecifiesawildcardcharacterthattriggerstheimportof
morethanonefile,alphabeticalorderdetermineswhichpackageisimportedfirst.
TheOptionalAppLinksparametermightappearasOptionalAppLinks=a.exe;b.exe;plugins\*.exe.
Usinga.exeandb.exe
assampleexecutablefiles,ThinAppimportslinkedpackagesintheorderdescribed
inTable 4‐1.
Forinformationaboutnestedlinks,see“SetUpNestedLinkswithApplicationLink”onpage 58.
Table 4-1. Imported Linked Packages
Import
Order Linked Package
1Baseapplication
2 a.exe
3 b.exe
4Plug‐insloadedinalphabeticalorder
5Nestedplug‐insfora.exe
6Nestedplug‐insforb.exe
7Nestedplug‐insforthefirst setofplug‐insinthislist