#SNAGIT INSTALL UPDATE#
#SNAGIT INSTALL WINDOWS 10#
#SNAGIT INSTALL OFFLINE#
#SNAGIT INSTALL DOWNLOAD#

The Download the WebView2 Runtime section of the Microsoft Edge WebView2 page provides several options for distributing the WebView2 Runtime onto client machines. Understanding the options at the Runtime download page The Fixed Version runtime can't be installed by using an installer. More disk space is required on the client, if there are multiple WebView2 apps installed.

#SNAGIT INSTALL UPDATE#

The WebView2 Runtime isn't automatically updated on clients, so to use the latest WebView2 APIs, you must periodically update your app together with the updated WebView2 Runtime. You need to manage the WebView2 Runtime yourself. Your app doesn't need to test whether the latest APIs are present. You know which WebView2 APIs are available to your app, because you control which version of the WebView2 Runtime is available to your app.

You have more control over versioning of the WebView2 Runtime.

The WebView2 Runtime that you package with your app is used only by your WebView2 app, not by any other apps on the client's machine. In the Fixed Version distribution mode, you download a specific version of the WebView2 Runtime and package it together with your WebView2 app in your app package. The Fixed Version runtime distribution mode See Details about the Evergreen Runtime distribution mode below. Even if your app uses the Evergreen distribution mode, we recommend that you distribute the WebView2 Runtime, to cover edge cases where the Runtime wasn't already installed.

#SNAGIT INSTALL WINDOWS 10#

Microsoft installed the WebView2 Runtime to all eligible Windows 10 devices, as described in Delivering Microsoft Edge WebView2 Runtime to managed Windows 10 devices. The Evergreen Runtime is preinstalled onto all Windows 11 devices as a part of the Windows 11 operating system. Your WebView2 app cannot specify that a particular version of the WebView2 Runtime is required.This linking provides benefits for disk footprint, memory, and performance. On eligible systems, binaries for Microsoft Edge and the Evergreen WebView2 Runtime are hard-linked together when they are on the same version. Less disk space is required for the WebView2 Runtime on client systems, because the WebView2 Runtime is shared by all WebView2 apps that are on the client. The underlying web platform (WebView2 Runtime) updates automatically without more effort from you. The Evergreen distribution mode is recommended for most developers. You can then distribute updates of your WebView2 app that use the latest WebView2 APIs, from the latest WebView2 SDK. Afterwards, the WebView2 Runtime is automatically updated on client machines.

#SNAGIT INSTALL OFFLINE#

In the Evergreen distribution mode, the WebView2 Runtime isn't packaged with your app, but is initially installed onto clients using an online bootstrapper or an offline installer. There are two different ways of distributing and updating the WebView2 Runtime to client machines: the Evergreen distribution mode, and the Fixed Version distribution mode. For example, a user doesn't have a browser desktop shortcut or an entry in the Start menu. After the WebView2 Runtime is installed, it doesn't appear as a user-visible browser app. The WebView2 Runtime contains modified Microsoft Edge binaries that are fine-tuned and tested for WebView2 apps. The concept is similar to Visual C++ or the. The WebView2 Runtime is a redistributable runtime and serves as the underlying (or backing) web platform for WebView2 apps. When you distribute your WebView2 app, you need to take into account how the WebView2 Runtime is distributed to and updated on client machines. When releasing an app that uses Microsoft Edge WebView2, you need distribute the WebView2 Runtime, either by distributing the automatically updated Evergreen Runtime, or by distributing a Fixed Version of the Runtime.Ī WebView2 app depends on the WebView2 Runtime on client machines.

Snagit install