Utilizing a ThinApp'ed Internet Explorer with a AppStack'ed Java

We have a few programs that interact with Internet Explorer, but the parts that integrate with Internet Explorer are not functioning correctly. Our Internet Explorer is ThinApp'ed, while the other applications are AppStack'ed.

I've tried modifying the Package.ini to allow entry points, hoping that it would allow entry points from an AppStack'ed or native program - but it's actually looking for the file and not finding it, so it's failing.

How do you get a ThinApp'ed Internet Explorer to play well with AppStack'ed programs?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

For any program to interact with a ThinApp packaged application (in this case, IE), it must be either captured/packaged with the application (i.e. Internet Explorer) or executed through the ThinApp package.   It sounds like you are doing the later here - running the native app through the virtual memory space of the ThinApp package.

App Volumes provisioned applications which are delivered to a desktop (via an AppStack or AppStacks) will run like any other natively installed application (I won't dig into the exceptions here).

The ThinApp entry point for the natively installed app must point to correct source location in order for it to run correctly - but with App Volumes in play, this source path may change based upon the desktop OS type.

To get the native app working through the ThinApp package, I would first eliminate all the unnecessary parts such as App Volumes....just to ensure it actually functions correctly.  Once accomplished, the next task is to ensure the correct path is called from within the ThinApp package for the native application residing on the App Volumes AppStack.  You will likely need to use system and ThinApp folder macros.   You'll also likely need to use the CommandLine= option within the Entry Point settings in the PACKAGE.INI file.

Your best bet is to enable the CMD entry point in the PACKAGE.INI and try manually browsing to and launching the application via the command line (don't launch explorer.exe from this command line as it likely won't work if you don't have "separate explorer processes" enabled in Windows).

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
FirstcomAuthor Commented:
Thank you for the explanation!

My issue that I need to assign the AppStack to the ThinApp VM before I started provisioning.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.