VMware Thinapp: Launching Native installed Application from VMware ThinApp Bubble

VMware Thinapp: Launching Native installed Application from VMware ThinApp Bubble.

1. In normal desktops, while launching some of the native installed application, some other application add-ins or tool bar are loading by default. But in VDI environments if the application is virtualized by VMware ThinApp, native applications will not recognize Thinapp packaged
applications.
2. Some natively installed application may require integration with Thinapp packaged application, but native application usually cannot
recognize Thinapp packaged application

Example:

I have VMware VDI environment using non-Persistant linked clone VDI desktops. Office 2013 is installed natively on all VDI desktops, but
Endnote 8 application is using via VMware ThinApp. In normal desktop environments, while launching "MS Word", Endnote tool bar menu will appear.
Since here I am using EndNote via Thinapp, Natively installed "Word" will not recognise ThinApp Packaged EndNote. Endnote package is packaged
application which is not installed on the machine. Endnote ThinApp always launch on Virtual bubble.

Solution:

Execute the native installed application from virtual bubble. Natively installed application will execute inside the virtual bubble and all

native and packaged components will be availble on lauched application.

Steps:

1. Create a shortcut file of natively installed application. Example "word.lnk" which points to "C:\Program Files\Microsoft Office\Office15\Winword.exe"
2. Go to "ThinApp project directory" and  Copy the shortcut file inside %drive_C%.
3. Edit package.ini and add below entry to enable new Thinapp Entry point.

[WordWithEndNote.exe]
Source=%drive_C%\word.lnk
ReadOnlyData=Package.ro.tvr

4. Rebuild the Thinapp by executing "build.bat" inside project directory.
5. Once build complete, new entry point will be created with name "WordWithEndNote.exe".
6. Publish this entry point to users who need to work "word" with "Endnote"
7. Configure File Type Association (FTA) accordingly to ensure all work files are lauching with this entry point by default.