You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue we are facing is that WebView2 is, bluntly, unwieldy and complicated in comparison to the old dead-easy-to-implement WebBrowser .NET Framework control. Embedding WebView2 within a single file class library appears to be next to impossible, at least without a lot of hoop jumping, mainly due to the unmanaged WebViewLoader dlls. In cases like ours where the browser isn't a core component of the solution (initial oAuth2 authorization, for example), a "lite" version of a browser control that is a small single file reference without dependencies (and no external runtimes, etc required) would be a blessing. Aka, an updated WebBrowser control that supports CSS3 and Javascript would be all that we - and I think a lot of other people - would need.
We have looked at upgrading from WebBrowser to several alternatives including WebView, CefSharp, Gecko, etc and none are ideal for various reasons. (WebView suffers from an inexplicable inability to function with elevated rights.) So a stripped down version of WebView2 might be a winner.
@protegesolutions - Can you be more specific in what you're actually looking to minimize? You're combining a lot of things and it's difficult to parse what you're looking for.
For something like OAuth, I believe most apps use the user's preferred browser, is a WebView needed for that case? Also, despite IE's deprecation, the WebBrowser control isn't going anywhere, so you can continue to use it if it's meeting your needs.
The issue we are facing is that WebView2 is, bluntly, unwieldy and complicated in comparison to the old dead-easy-to-implement WebBrowser .NET Framework control. Embedding WebView2 within a single file class library appears to be next to impossible, at least without a lot of hoop jumping, mainly due to the unmanaged WebViewLoader dlls. In cases like ours where the browser isn't a core component of the solution (initial oAuth2 authorization, for example), a "lite" version of a browser control that is a small single file reference without dependencies (and no external runtimes, etc required) would be a blessing. Aka, an updated WebBrowser control that supports CSS3 and Javascript would be all that we - and I think a lot of other people - would need.
We have looked at upgrading from WebBrowser to several alternatives including WebView, CefSharp, Gecko, etc and none are ideal for various reasons. (WebView suffers from an inexplicable inability to function with elevated rights.) So a stripped down version of WebView2 might be a winner.
AB#40760906
The text was updated successfully, but these errors were encountered: