Reply to Message

View discussion in a popup

Replying to:
Theike
Hot Shot
Hot Shot

Hi,

First a welcome to the forums...

Short answer: you don't/can't...

To set the 'default emailclient' this would involve altering the native systemsettings and the purpose of ThinApp is to 'shield' the system from such settings. You have to see it as follows:

When you capture an application and a mail client in a single package, the application (that has a 'send email' feature) would see the features end configuration provided by the virtualisation wrap. (as intended). For the native system however there are no settings that have been altered to allow sending email.

For example the (most common) interface to send email from an application is using the MAPI interface. This is used by the Microsoft products like outlook (express). If you would have no email client at all on your system this interface would not have been configured. To the system your email client would not be there at all. A ThinApp application in general is nothing more than a single EXE. You don't install any local 'services'. Using ThinReg (or MSI install) to do the registration of general handlers (.doc = ThinApp WinWord) or add the shortcuts to the startmenu are 'just' convinience accessors. They will not be able to provide the services/configuration needed for this.

With ThinApped applications you just don't want your local system to be 'corrupted' with undesired settings. And in general... We don't use ThinReg or the MSI option as it also introduces some undesired or uncontrolable behaviour. Eg: Office 2003 and 2007, thinapped & 'installed' using MSI or ThinReg: which one opens '.doc' depends on which one was 'installed' first. This is undesired in a professional environment in which you want consistent behaviour...

If the other applications are ThinApped as well, you could applink it. In that case the application would see the application...

It is possible to modify the local system to get a configuration in which the MAPI interface get's installed locally and it could call the virtualised email client. But i think you would mis the point with desired results (you would still be modifying the native system beyond simple recovery, which the packaging and virtualisation targets)

Kind regards,

Michael Baars - Comprehensive ICT solutions

(Please remember to mark the question aswered if so and reward points to those who helped you)

Michael Baars - Comprehensive ICT Solutions (NL, Weert) (Remember to mark the post answered and reward points to those who helped you...)