Contents - Index - Top


WebView2LoaderPath

Interface AntView and AntViewGlobal

 

Type: Property

Access: Read/Write

Data Type: String

 

 

Default is ""

 

Using WebView2LoadPath you can provide an alternative location for the webview2Loader.dll provided by Microsoft.

The default location is to have it installed in the same location as your binary, as that way Windows will be able to locate it via the normal Windows Search Path.

However sometimes that is not ideal. With this property you can install the .dll in a path of your own choosing.

 

If you want to troubleshoot this then take a look at generating a troubleshooting log as there you can find from what location the webview2loader.dll is loaded.

 

Here's an example for what you would be looking for in the following log snippet, we did set our WebViewLoader2Path to "D:\Test":

 

 2022-02-24 23:58:19.165 Reading InstallPath = 

 2022-02-24 23:58:45.529 Trying to load the loader DLL as D:\Test\WebView2Loader.dll

 2022-02-24 23:58:53.940 Loading from WebView2LoaderPath : success.

 2022-02-24 23:59:01.759 Loaded as D:\Test\WebView2Loader.dll

 2022-02-24 23:59:01.759 Version = 1.0.1108.44

 2022-02-24 23:59:01.759 Assigned loader library procedures.

 

As you can see there the loader DLL was found and loaded without problems. 

The .dll version is 1.0.1108.44

 

The actual search order is as follows:

- First comes the path set via WebView2LoadPath

- Next, if on a machine where the AntView installer was used to install the AntView component, it will look for the loader.dll in the AntView installer path.

- Finally it will search via normal Windows Search path, which starts at the location of the binary under which the AntView control is hosted.

 

This property can also be set via the AntViewGlobal object instance for all of the AntView controls in your application.

 


AntView - The MS Edge WebView2 ActiveX control Date last changed: 09/25/2024