eddys's avatar
eddys
Senior Member
7 years ago
Status:
New Idea

Add Support for Windows Application opening a Second application Utilizing DotNetBrowser

When opening an application that uses DotNetBrowser through a Windows Application (WPF), we should be able to access the DotNet application's content including all of its cell data. 

 

Currently, we are presented with a message regarding "Chromium Embedded Content." When recording or using Object spy to identify cells within the application's window, one big red outline covering the entire window is the only cell we are offered. There is no way to identify subcells within this larger cell and the object tree reflects this problem. 

 

We are aware the problem is not actually related to Chromium Embedded Content but rather TestComplete does not support DotNetBrowser. 

 

The team would appreciate any feedback or help from anyone who has experienced this as well. Thank you. 

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    7 years ago

    Do you have a license for Web along with your Desktop module license?

     

    In order to run tests with embedded browsers, regardless of the technology, you need a Web license along with your Desktop license.

  • eddys's avatar
    eddys
    Senior Member
    7 years ago

    We are running the trial version which contains both Desktop and Web modules active. 

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    7 years ago

    At this time, based upon the documentation, DotNetBrowser, as you noted, is not supported.

     

    Not sure what exactly to tell you to do.  There are options to use OCR or TextRecognition to recognize controls within that window based upon text.  You might also want to activate MSAA for the control and see if that works.