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

Using MSI to distribute packages


When deploying a ThinApp package locally, the most common method is to use the MSI format. That being said, you could very well just copy the package down to the client's hard drive. ThinApp can generate an MSI wrapper around the package. Any deployment tool supporting the MSI format can use the MSI file. You can activate creation of an MSI file by deleting the semicolon in front of the MSIFilename parameter in Package.ini and running build.bat.

There are two different MSI file formats that you can create. The first alternative is a self-contained MSI file, containing both the MSI logic and the actual package files (entry points and the data container). The second alternative keeps the package files outside the MSI file. If you choose to have the package files outside the MSI file, the MSI file and the package files must all be located in the same folder. MSIStreaming is the parameter defining which MSI format you'll compile. MSIStreaming=0 will create a...