Edge WebView2 Object Plugin

The Edge WebView2 object lets you display a web site on the page or dialog, just like it would appear in the Chromium-based Edge web browser. It does this by taking advantage of the Microsoft Edge WebView2 control that needs to be present on the target system. Specifically, it embeds this control directly into your AutoPlay application at run time. This essentially places the Edge rendering engine on your page and uses it to display HTML in your application. The end result is pretty much the same as what you would see in Edge itself, except that the desktop browser interface is not visible. Therefore it looks like the web page is built right into your application. You can use it to display online web content on the Internet, or to display locally stored web pages directly off a CD-ROM (or the user's hard drive).

Dependency module

This plugin comes with a dependency module, which you should add to your project, in order to make sure that the required Microsoft Edge WebView2 runtime is available on the target computer. Without this component, the Edge Webview2 will not load and no content can be displayed. If the runtime is not detected, it will allow the download of the online installer, before opening your application.

Documentation and sample project

The actions and functionality provided in this new object plugin was designed to match the original Internet Explorer-based Web object as closely as possible. If you ever used the Web object, you will have no issues with the Edge object.

The plugin comes with an HTML help file, explaining all available functions. Also, a sample project (*.apz) is provided, which you can import into your workspace and run, to see the new object in action immediately.

Cache and cookies

The Edge WebView2 Object will store its browsing cache and cookies in the user's LOCALAPPDATA. This approach allows to keep preferences, settings, logins, cookies etc. between sessions.

When built as a web/email executable, the AutoPlay Media Studio application would decompress itself in the user's TEMP folder, and there the cookies would also be stored. However, on finishing/closing the application, all data is removed from the temporary folder, and by doing so, all cache and cookies are lost. By saving the data in the application data folder, information is kept, making the use of the WebView2 component less annoying for the end user. Of course, if desired, the cache and cookies can manually be cleared by deleting the folder contents.

The typical path for the cookies is:


For an AutoPlay Media Studio application built for web/email, the name would be "autorun.exe". If you publish the application to a hard drive folder or USB drive, it may have any name.

Software Compatibility

AutoPlay Media Studio 8

Support Policy

All software products were tested and found to work, but they are provided without any explicit guarantee that they will work in every possible environment without further customization. If you need support or consulting, please contact me.


This product is now part of AutoPlay Media Studio 8.6 and newer, and can no longer be downloaded from here.


You can purchase a license for AutoPlay Media Studio here with 10% off. Upon clicking the button below, you will be taken to Indigo Rose's website, where you will complete the transaction. The order fulfillment is handled directly on their website, and it will display the aforementioned discount.

And of course, once you have a license for AutoPlay Media Studio, you could request this software extension for free.

Purchase AutoPlay Media Studiofrom Indigo Rose Software