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

Modifying the project folder


Applying changes directly to the project folder is a very efficient and easy method of updating your packages. This method is mostly used when applying configuration changes, and patching and hotfixes. Using this update method requires that you know where changes are to be applied and how. If the configuration change is a simple change of a registry key, it's easy enough to open the registry text file, find the key, and change it. If you need to change a configuration file within your virtual environment, it's a simple matter of opening the file in Notepad and making the modification. If the update is delivered to you as files with documentation on where they should be copied, many times replacing the existing versions, case, I would personally use this method of updating. One big advantage of using the modifying the project folder method is that all your original Package.ini settings are preserved. If you want to use MSI for deployment of the new version, you...