1. Aron Cox
  2. PowerBuilder
  3. Thursday, 19 May 2022 13:56 PM UTC

Sorry, second one today.

PowerBuidler 2019 R3 build 2728

Windows 10

We have switched all our old Internet Explorer activeX controls to the new PowerBuilder web browser control and everything works great, until our .NET developers changed our login window from a standard PowerBuilder window to a .NET window that has embedded the lastest version of the Chromium Enbedded Framwork.

Now whenever we try to use any of our PowerBuilder web browser control windows PowerBuidler crashes, it reports a fault in libcef.dll. I can only assume because the .NET window has loaded a different version into memeory and PowerBuilder is now unhappy.

This leaves me with a few questions:

* Can I find out what version of CEF PowerBuilder is using?

* Anyone got any clever ideas of what to do apart from making them both use the same version (becuase they tell me they need the newer version)?

Thanks!

Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 19 May 2022 14:08 PM UTC
  2. PowerBuilder
  3. # 1

Check the file libcef.dll in the pbcef folder (under the PowerBuilder runtime folder).

PB 2021 Build 1509 has version 3.3626.1984

 

Comment
  1. Aron Cox
  2. Thursday, 19 May 2022 15:00 PM UTC
Thanks, somewhat interestingly the .NET team's libcef.dll reports this version 97.1.6 which seems very different !?!
  1. Helpful
  1. Arnd Schmidt
  2. Thursday, 19 May 2022 15:39 PM UTC
Normally you can navigate to the url:

chrome://version/

There you will see the CEF and the current Chromium Version:



This is from PB 2019 R3:

CEF: 3.3626.1894.g90eb8cc

Chromium: 72.0.3626.96

OS: Windows

WebKit: 537.36 (@84098ee7ef8622a9defc2ef043cd8930b617b10e)

JavaScript: 7.2.502.25

Flash:

User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.96 Safari/537.36

...



hth

Arnd
  1. Helpful 3
  1. Aron Cox
  2. Friday, 20 May 2022 15:05 PM UTC
Ahah, thanks. Seem the .NET guys are using a much more recent version, and I guess that's the problem :( For now we're having to take out all code that uses the new web browser control from all our applications :(
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.