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

Some packaging tips


Over the years I've collected a couple of tips and tricks when performing packaging. The following is a collection of the most important and frequently used ones.

32-bit versus 64-bit

The easiest method of creating a ThinApp package is to always capture it on the same operating system as the package will be used on. But this is not always possible. There are many reasons why you would want your package to support multiple operating systems, and in those cases you must capture it on the lowest common denominator. A 32-bit application captured on a 32-bit operating system, running in a 64-bit environment, is a special kind of beast. The most common reason for trouble is the fact that the Program Files folder change names. When a 32-bit application refers to %ProgramFiles%, the OS will provide C:\Program Files (x86) as the path. But still a 32-bit application can access the C:\Program Files folder. Let's say the application uses XML files and .ini files for configuration....