Skip to main content

We've written a .net browser control that should provide the functionality we need post active-x (webbrowser2 is inadequate for our needs).  The issue we are having is with capturing events.  Could someone explain how to capture the .net control events in our COBOL program?  I know this has been asked before, but I do not see a resolution.  The dll has been registered and is in the run directory, and netdefgen has generated the def file.  We can display the control.  What's missing is the communication of events back to the COBOL program.  We are using the 10.5 runtime.  

We've written a .net browser control that should provide the functionality we need post active-x (webbrowser2 is inadequate for our needs).  The issue we are having is with capturing events.  Could someone explain how to capture the .net control events in our COBOL program?  I know this has been asked before, but I do not see a resolution.  The dll has been registered and is in the run directory, and netdefgen has generated the def file.  We can display the control.  What's missing is the communication of events back to the COBOL program.  We are using the 10.5 runtime.  

Our sample\\dotnet\\NETOBJECTS provides an example of using .Net assemblies and responding to their events. I also know, Acu Dev had to fiddle with WebView2 a lot to get it working. I'll see if we can provide as many tips as possible.

Our sample\\dotnet\\NETOBJECTS provides an example of using .Net assemblies and responding to their events. I also know, Acu Dev had to fiddle with WebView2 a lot to get it working. I'll see if we can provide as many tips as possible.

Hopefully you've been able to get events. Even though you're not using our browser2, these variables may hold clues as to how Web-View2 interacts. They won't be valid for how you are using web-view2, but you may need to do similar types of things to get web-view2 working properly.

WEB-BROWSER2 control:

  • WIN32_BROWSER2_FOLDER
  • WIN32_BROWSER2_VERSION
  • WIN32_USER_DATA_FOLDER
Terms & ConditionsAccessibility statement