There is no mechanism to deploy ThinApp packages together. When a ThinApp package is
dependent on another ThinApp (Applink), they have to be deployed separately, followed by
adding the Applink path in the ThinApp package.ini (OptionalApplinks or RequiredApplinks).
Further, it requires rebuild of the ThinApp to pick up the Applink path.
This whole process of finding out the Applink path, updating package.ini, rebuilding the
ThinApp are completely manual and cannot be automated.
Get ready for application virtualization with VMware ® ThinApp ® !
One great benefit of ThinApp’s bubble-to-bubble communication feature, called AppLink, is that you can have application dependencies assigned either static or dynamic. This will allow you some great flexibility but can just as easily make your design quite complex. As always, just because we support a feature or a usage of a feature doesn’t necessarily mean you should use it. In this blog post will I tell you about some of the functionalities of AppLink and then leave it up to you to decide how you’ll implement it…