title: WebView2Loader.dll vs WebView2.dll
body: <p>The company I work for developed an application that uses WebView2 to display a Edge browser within the app. The IDE we use (Delphi) provides a dll called &quot;WebView2Loader.dll&quot; to distribute along side the exe.</p>
  <p>When looking at how the WebView2 runtime operates, there are a lot of mentions of something called &quot;Evergreen&quot; which seems to be the WebView2 runtime that auto updates itself to the latest and greatest.
  <a href="https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution#understand-the-webview2-runtime-and-installer-preview" rel="nofollow noreferrer">https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution#understand-the-webview2-runtime-and-installer-preview</a></p>
  <p>This is where the confusion came in. My question is how does this Evergreen relate to the WebView2Loader.dll? The way I think it works is that the loader dll is only there to find the installed WebView2 runtime and the Evergreen is actually doing the downloading of the runtime. I get this indication from this quote &quot;WebView2Loader.dll is a small component that helps apps locate the WebView2 Runtime, or non-stable channels of Microsoft Edge, on the device.&quot; from this link <a href="https://docs.microsoft.com/en-us/microsoft-edge/webview2/how-to/static" rel="nofollow noreferrer">https://docs.microsoft.com/en-us/microsoft-edge/webview2/how-to/static</a>.</p>
  <p>And then my follow up question would be, would customers have to download Evergreen manually or would that runtime exist if they have edge installed already?</p>