Advice Needed: Integrating Multiple WebBrowser Controls for Unified PC RT Screens in a C#.NET HMI Application
0
Hi all, I am working with a customer who want to upgrade their C#.NET-based HMI desktop application with WebBrower controls in their Windows Forms. These WebBrowser controls would present Unified PC RT screens, which would be conceived and scaled to fit for certain areas of their Windows Forms. The C#.NET application would thus be augmented with what Unified does well, such as Alarm Views, machine-specific operator "panels", etc. No faceplates or pop-ups are planned to be used, just a basic screens with no navigation going on within the Unified screens themselves. The C# application and Unified PC RT would be on the same IPC. Can anyone advise on the constraints of such an approach? Removing client license counts as a factor, would it be possible to have multiple WebBrowser controls showing different Unified screens on a single Windows Form? Also, where multiple Windows Forms in the .NET desktop application are concerned, could those forms also present additional Unified screens (via multiple WebBrowser controls)? The .NET application would manage the user authorization strategy whereby the Windows Forms would maintain control of which Unified screens are presented, etc. Accounting for limits to the amount of web client connections and resources available in Unified RT PC, is more than one WebBrowser control per Windows Form (or Forms) doable? I would estimate that the .NET HMI application would require up to 3 WebBrowser controls presenting Unified screens on any given Windows Form - but typically only 1. Thank you very much in advance!