Embedding Web Client in custom application

Behavior:

In a custom Application which is using Webbrowser Control to open a URL Integration, it is not possible to set stamps.

Solution:

The problem here is that by default the webbrowser control, if nothing is set, uses IE 7.
Please consider following important notes: 

IE Browser Control options that reflect DocuWare Web Client Integrations
The following sections contain information of System Registry values, which reflect the work of standard IE WebBrowserControl. Each one will be described with registry path to the value, how it reflects integration’s work, and what is the value that need to be set in order for our code to work correctly.

1. Legacy Mode – determines whether the legacy input model is enabled. By default, the feature is disabled for Internet Explorer and enabled for applications hosting the WebBrowser Control.

When Legacy input mode is enabled, the following conditions are true:

• Windows pointer messages are not processed by the rendering engine.
• Document Object Model (DOM) pointer and gesture events do not fire.
• Mouse and touch messages are dispatched according to the Windows 7 input model.
• Touch selection follows the Windows 7 model ("drag to select") instead of the Windows 8 model ("tap to select").
• Hardware accelerated panning and zooming is disabled.
• The Zoom and Pan Cascading Style Sheets (CSS) properties are ignored.

DocuWare WebClient is using pointer events, and enabling this mode may harm the functionality. Some of the other points could also be a burden. To disable this feature by using the registry, add the name of your executable file to the following setting:

HKEY_LOCAL_MACHINE (or HKEY_CURRENT_USER)
  SOFTWARE
   Microsoft
    Internet Explorer
     Main
      FeatureControl
       FEATURE_NINPUT_LEGACYMODE
         Process_name.exe = (DWORD) 00000000

“Process_name.exe” is the name of the process, which encapsulates the browser control. For example, for WEC this is „DocuWare.PlatformUIProcess.exe“.

2. Browser Emulation – It seems that by default the browser control is not using the latest installed version of Internet Explorer. That’s why sometimes it is necessary to set the version of IE, which we want the control to use. Here is the suitable registry key:

HKEY_LOCAL_MACHINE (or HKEY_CURRENT_USER)
  SOFTWARE
   Microsoft
    Internet Explorer
     Main
      FeatureControl
       FEATURE_BROWSER_EMULATION
         Process_name.exe = (DWORD) 00009000

 The following table gives the options for the value:

3. Outlook limitation – This limitation is not related to a Registry value. It is rather something that comes from Outlook. By the date of writing this document, all integrations initiate signalR connection to the server in order to receive push notifications.
It seems that Outlook has connection limit and when you have several integration, each in separated browser control, you cannot load all of them neither can make server calls from the loaded ones. This should be taken into consideration when opening different integrations in Outlook.
Alternative: Use GeckoFX Engine: https://code.google.com/p/geckofx/