Book Image

VMware ThinApp 4.7 Essentials

By : Peter Bjork
Book Image

VMware ThinApp 4.7 Essentials

By: Peter Bjork

Overview of this book

VMware ThinApp 4.7 is an application virtualization and portable application creator which allows users to package conventional applications so that they are portable. "VMware ThinApp 4.7 Essentials" shows you how to deploy ThinApp packages in order to improve the portability, manageability and compatibility of applications by encapsulating them from the underlying operating system on which they are executed. Application virtualization improves the portability, manageability and compatibility of applications by encapsulating them from the underlying operating system on which they are executed. VMware ThinApp 4.7 is an application virtualization and portable application creator which allows users to package conventional applications so that they are portable. ThinApp eliminates application conflicts, reducing the need and cost of recoding and regression testing. In this book you will learn about how application virtualization works and how to deploy ThinApp packages. You will learn how to update and tweak ThinApp Projects before distribution. This book will then cover design and implementation considerations for future ThinApp projects.
Table of Contents (15 chapters)
VMware ThinApp 4.7 Essentials
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Packaging applications with dependencies


There are three kinds of application dependencies as I see it:

  • Dependencies on runtimes such as Java or Flash

  • Dependencies on locally installed applications

  • Dependencies on another virtualized application, for example, packaged Internet Explorer integrates with packaged Adobe Reader

Dependencies on runtimes

When it comes to dependencies on runtimes, there are different strategies you can choose for your deployment methods. My favorite, for most of the environments, is having the latest, greatest runtime version locally installed. Most of your applications can use this version and the ThinApp packages can make use of natively installed components.

I tend to package together only the application that requires a really old version of the runtime with its dependencies. Now I have one single self-contained package including both the application and its dependency.

If you have a couple of applications requiring the same special version of a runtime, I would use...