Another callout is that the API cannot handle offline install (because under the hood the API is basically doing the online-only deployment flow in option 1). Selecting Make Optional for an extension removes the extension requirement. Select the extension, then select Require Extension from either the right-click menu or the ribbon. Expand Updates and Servicing and select the Console Extensions node. It’s likely a simpler developer experience if your install stack can include our header and call our API, or you're just trying to call it at app runtime, but it may be complicated if your install stack can't call arbitrary APIs (WiX may be an example). In the Configuration Manager console, go to the Administration workspace. Option 2 - We can expose an installWebView2 API inside our SDK that installs WebView2 without elevation. Essentially, your installer will be detecting if WebView2 is already installed, and if not chain install our installer that is either packaged with your installer or downloaded on the fly. The developer experience of using those would be similar to our current per-system installer (see online-only and offline deployment on ). Option 1 - We can expose a small online installer (and a stable link to it so that you can download it from the client device rather than) and a full offline installer that can install WebView2 without elevation. Hey folks, we’re currently evaluating a couple potential options (not final) to install WebView2 without elevation and we would love to hear any input/preference from you all.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |