The runtime searches for DLLs after it has searched for COBOL programs. It first searches the paths defined in the CODE_PREFIX configuration variable, and then in the System and Windows folders. You can use the runtime -y option and have the PATH to the dll in each -y option 

-y lib1.dll -y C:\my-dir\lib2.dll -y C:\my-dr2\lib3.dll  and there is a runtime configuration variable

SHARED_LIBRARY_LIST

None of these suggestions work for me.  When I add dll's to the SHARED_LIBRARY_LIST, using the command line switch, or setting the environment variable programatically, a trace shows that these libraries are loaded, but the .net control does not work.  The program is looking for the dll in the runtime directory.  When the dll's are in the runtime directory, there is no reference in the trace that they are loaded, but it works.  This is a deployment issue.

.Net controls are different than calling dlls - update NetEvents.ini with the directory path of the event handlers. NetEvents.ini must be in the same directory where the runtime is located.

I tried that as well, but it did not work.

I'll guess that this has to do with using web-view2, if so, we noticed that there are a great number of instances of how Microsoft makes Web-View2 modules available.  When setting up the user environments, is the Path to Acu and your web-view2 dlls, first in the PATHING?

Does 'user environment' refer to path settings in control panel, or CODE-PREFIX in cblconfig, or something else?

ftp://ftp35@amerftp.microfocus.com/shjerpe/env.jpg  2 environments, 1 is set typically within the Control Panel. Some customers create a bat file to set their environment, others use COBOL accept from or Set phrase to set the environment. wrun32 -c my.cfg - in this case the variables within the config file like CODE-PREFIX are loaded first. When using the web-view2 dll you are using, are you registering it on the user machine, does that registration succeed? As a .Net assembly, there may already be web-view2 assemblies in the GAC - https://learn.microsoft.com/en-us/dotnet/framework/app-domains/gac  if that is true, I'm not sure what you need to do, to make sure yours is the one that will be used. CODE_PREFIX is used for COBOL calls, I'm not sure it applies to the .Net assemblies. the -y mentioned above is for dlls (and COBOL calling dlls), but not .Net assembly dlls. The .Net assemblies have the runtime bring in the Microfosoft CLR in order to use and work with the .Net assembly.

I am able to successfully register the webview2 browser control we have developed on my local machine.  As long as the browser dll and tlb files are in the runtime directory (along with some Microsoft webview controls), I am able to display and manipulate the control.  Otherwise, I get the following error: