office-365With the release of Act v18, Swiftpage announced that it is now fully compatible with MS Office 2016, provided, of course, the version of Office is not 64-bit or Click-to-Run (CTR). The trouble is that telling the difference between the full on-premise version of Office 2013 and 2016 and the CTR versions is not quite as simple as you might guess. This has left many in the dark as to whether their seemingly "installed" version is, in fact, compatible with Act! v18.

The following article describes how to make that determination...

 

 
 

How to: Determine Whether Outlook Is a Click-to-Run Application on a Computer

 
Office 2013 and later

 

 

 

 

 

 
 


Click-to-Run is a software delivery and updating mechanism available to Office 2010 and later versions. Products delivered via Click-to-Run execute in a virtual application environment on the local operating system. This means that they have private copies of their files and settings, and that any changes they make are captured in the virtual environment.

Click-to-Run is fast—users can start running an application within a short time without waiting for the complete product to finish installing. Updates are run automatically in the background, without requiring a user to first remove an installation or manually install updates. Click-to-Run products are virtualized and do not conflict with other installed software. However, because a product delivered by Click-to-Run has private copies of all its files and registration, an add-in developer cannot determine the product’s existence in the same manner as a product that was installed on a client computer’s hard disk. Starting with Outlook 2010, add-in developers should verify whether Outlook has been installed, and whether Outlook has been delivered as a Click-to-Run product.









 
Note
Only 32-bit Office 2013 is supported in the Click-to-Run virtual application environment, even if the client computer runs a 64-bit operating system.
 

To check whether Outlook 2013 was delivered by Click-to-Run on a client computer

 
 

  • Verify whether the VirtualOutlook key exists in the following location in the Windows registry:HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Office\15.0\Common\InstallRoot\Virtual\VirtualOutlookThe VirtualOutlook key is a REG_SZ value that contains the culture tag of the installed product language, such as "en-us".





  •  
  •  
  •  
  •  

 

2016-04-28 20:47:00
 
Comments List