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

Default isolation modes


Isolation modes are probably the most important feature of ThinApp and therefore one of the most interesting in my opinion. When it comes to configuring your packages, isolation modes are of course a centerpiece.

When I create a ThinApp package, I always start using WriteCopy as my default directory isolation mode. This way all changes I do during my test runs will end up in the sandbox. This is important because it lets you get to know the behavior of the application, that is, learn what will end up in the sandbox. Why this is important we will discuss in more detail in the next chapter. When I'm ready to compile my production ready package, I usually change the default directory isolation mode to Merged. This way, the package will act like a natively installed application. It will for many locations honor the permissions specified on the client OS. For example, if a user tries to save a document in the root of the C:, a denial dialog box will be displayed to the...