| Tweet |
I have come across a scenario where the customer has lost the ThinApp project folders and left with ThinApp EXE. As the project folders are required to generate MSI, the package could not be deployed with VMware View due to missing MSI. Instead of recapturing the application to generate MSI, the solution proposed below shall allow tweaking another ThinApp MSI (where MSIStreaming=1 is set) by editing the respective MSI tables and contents. Continue reading
| Tweet |
Limitation:
There is no mechanism to deploy ThinApp packages together. When a ThinApp package is
dependent on another ThinApp (Applink), they have to be deployed separately, followed by
adding the Applink path in the ThinApp package.ini (OptionalApplinks or RequiredApplinks).
Further, it requires rebuild of the ThinApp to pick up the Applink path.
This whole process of finding out the Applink path, updating package.ini, rebuilding the
ThinApp are completely manual and cannot be automated.
| Tweet |
Lakshmana Prakash
ThinApp Packaging Consultant
ThinApp Community: Lakshman
lprakash@vmware.com
Problem:
During initial launch of the ThinApp EXE, a new sandbox is created, which holds the runtime
modification of the application. After an uninstall of the ThinApp software the sandbox is not
deleted.
| Tweet |
White Paper on
ThinApp Conditional Install
Lakshmana Prakash
ThinApp Packaging Consultant
ThinApp Community: Lakshman
lprakash@vmware.com
Problem:
In general, there are many applications that might have been designed to work in a specific environment. Typical environments consist of the following:
1. Operating System Version (e.g. Windows 7 or Windows XP)
2. Operating system Service Packs (e.g. Windows XP SP3 or Windows Vista SP1)
3. Operating System Type (e.g Windows XP 32 bit or Windows 7 64 bit)
When capturing those applications, it is necessary to make sure that the ThinApp is
installed for that specific environment, by checking the system.
| Tweet |
I just was asked, since a ThinApp package can run as a regular user, can a ThinApp MSI be installed/registered as a regular user as well?
Of course!
| Tweet |
Recently I was asked if there was a way to pin ThinApp packages to the Start Menu and Taskbar in Win 7. Well, depending upon what your desired outcome is, there are both long and short answers.
Let's dig into them here…
| Tweet |
By following the examples below, it is possible to add 'Right Click' functionality, or Shell Extensions, to your ThinApp packages. In this way you can use Windows Explorer to send paths and file names as arguments to ThinApp executables before they launch.
| Tweet |
Many organizations with established software packaging practices have standardized their process to include ‘registry branding’ to indicate that an MSI was created by their packaging team, and to populate an area of the Widows registry with information that they can use for inventory purposes. Adding these custom registry keys to ThinApp generated MSI’s can be done very easily. Additionally, there may be times when you would like to launch a script, execute a file, or collect some information programmatically as part of the MSI installation process. Here are the steps you should follow to perform these functions within a ThinApp generated MSI.
| Tweet |
Some time ago, I got to thinking about if it was possible to replace a natively installed application with a ThinApp packaged application by use of ThinApp’s ability to create an MSI package.
After a couple of people recently ran this by me, I again started thinking about it and decided to test it out. And, as it turns out, my speculations were correct! It’s totally possible!
| Tweet |
It is mentioned in our manual but since I am getting a lot of question regarding this subject I thought I might as well post the answer here.
When it comes to using MSI and usage of a deployment tool (ESD) to update a ThinApped application is there three parameters being used. You find them under [BuildOptions] in the MSI Parameters section of package.ini.
