Outlook 2010 – 2016 doesn’t let you set WebViewUrl and WebViewOn
We’ve started a new line of blogs to inform Office [and Add-in Express] developers about [serious] problems [and solutions] related to Microsoft Office [and/or Add-in Express products] as early as possible.
This blog is about a recent change in Outlook 2010 – 2016: changing the WebViewUrl and WebViewOn properties of the Outlook.Folder (Outlook.MAPIFolder) object raises an exception. Outlook users who have a delayed access to Outlook updates may still be unaware of the issue.
To find out if your Outlook is affected by this issue, right-click an Outlook folder and pay attention to the Home tab: if the Home tab is missing, your Outlook is affected.
The only Add-in Express related aspect of this issue is: the WebViewPane region that Add-in Express provides to let you embed your forms into Outlook windows is affected; your form won’t be shown in that region if a corresponding Outlook update is installed.
Microsoft introduced this change to deal with a security issue.
Microsoft describes the issue and provides possible workarounds on this page. Note that it describes two issues; you may need to solve both of them.
The registry key to be changed depends on the Outlook version used. You need to specify the EnableRoamingFolderHomepages registry value in the following registry keys for the following Outlook versions:
In addition to the above said, that page describes a registry change that you need to do to let the WebViewUrl and WebViewOn properties work on a non-default Outlook message store.
20-Dec-2017. We’ve created a sample project that emulates the WebViewPane layout by turning off the Reading Pane and using the FolderView layout in an Add-in Express based add-in. The project is in C#; let me know if you need a VB.NET one. The project is here, the FolderView layout is briefly described here.