Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto dependency installation of WebView2 #2792

Merged
merged 2 commits into from
Aug 28, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion microsoft-edge/webview2/concepts/distribution.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,20 @@ ms.author: msedgedevrel
ms.topic: conceptual
ms.prod: microsoft-edge
ms.technology: webview
ms.date: 3/29/2023
ms.date: 08/21/2023
---
# Distribute your app and the WebView2 Runtime

<!-- todo:
mikehoffms marked this conversation as resolved.
Show resolved Hide resolved
Packaged apps can declare a dependency on WebView2 and it'll get installed if necessary. Mention this option, it's a simpler and more attractive option for many devs. No need to use Evergreen Bootstrapper, Evergreen Standalone Installer or SelfContained (Fixed Version) distribution.

Update this page to include this option

See https://learn.microsoft.com/uwp/schemas/appxpackage/uapmanifestschema/element-win32dependencies-externaldependency

(that has an example explicitly citing WebView2)
-->

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.

A WebView2 app depends on the WebView2 Runtime on client machines. When you distribute your WebView2 app, you need to take into account how the WebView2 Runtime is distributed to and updated on client machines.
Expand Down