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

[requirement] support Microsoft webview2 fixed version mode #11

Closed
congzhangzh opened this issue Oct 30, 2020 · 1 comment
Closed

[requirement] support Microsoft webview2 fixed version mode #11

congzhangzh opened this issue Oct 30, 2020 · 1 comment

Comments

@congzhangzh
Copy link

Purpose:

deploy .NET core webview_csharp application with self-include a fixed version WebView2 runtime.

Trouble:

webwiew windows implement need allow to pass browserExecutableFolder to CreateCoreWebView2EnvironmentWithOptions or auto detect some default subfolder like webview2. which is not possible now. the code 
ref:
1. https://github.com/webview/webview/blob/master/webview.h#L871
2. https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/webview2-idl?view=webview2-1.0.622.22#createcorewebview2environmentwithoptions

Why this will extremely useful?

As .NET  5 near to release,  Microsoft and .NET is cool again now, the single file release mode is cool, but once you depend webview2 runtime, you must provide an installer or depend on OS's install of Edge Browser, which is out of developer's control sometime.
 
I think webView + asp.net Blazor will be great solution for cross platform desktop application, although Microsoft's provide their full stack to these solutions, but they seems always under refactor & reArchitecture & refusion & competition, like https://github.com/xamarin/MobileBlazorBindings, https://github.com/dotnet/maui, https://github.com/Clancey/Comet, when Microsoft find the perfect solution and implement it, the developer depends on Microsoft lost all the chance and died:)

But we must say, some core part of Microsoft is cool, like .NET,  C#

, asp.net blazer, Edge itself, we can just mix the most reliable part of it, I have an Idea that Use WebView as asp.net Web Application container and show asp.net blazer content in it. use webview to show the website but not the trick way of mobilebinding as that's a work in progress product( I do not know how about their relation to maui), but balzor is the core foundation part which maybe more reliable and stable.

ref:

  1. Feature Request: Example project with Blazor UI framework? #4
  2. allow fixed version of WebView2 on Windows dotnet/MobileBlazorBindings#202
  3. Don't make Installer required MicrosoftEdge/WebView2Feedback#341
  4. https://docs.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution#fixed-version-distribution-mode
@geaz
Copy link
Member

geaz commented Nov 3, 2020

Fixed Version support has to be implemented by the core webview project: https://github.com/webview/webview
Please create a feature request over there. We have to discuss the best way to integrate it to the generic api.

EDIT: Saw you already did. So lets discuss it over there 👍

@geaz geaz closed this as completed Nov 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants