Skip to content
This repository has been archived by the owner on Jun 5, 2023. It is now read-only.

A better way to split webview container & hosted asp.net core containee #128

Open
congzhangzh opened this issue Nov 14, 2020 · 0 comments
Open

Comments

@congzhangzh
Copy link

I am a little worry that it's impossible to implementte a stable boudance to make this project stable, as it's really need update follow asp.net core's upstream change, make this project can not be standalone.

the only way is to use https://github.com/xamarin/MobileBlazorBindings, but mix asp.net core with heavy xamarin is not good idea, we just need the best part of asp.net core & webview.native.

I propose a better way to mix in process with asp.net core and cross platform webview which already implement by WebWindow, as the use http protocol as boundance is more stable and any asp.net core in the future will follow.

So use the webwindow's native webview & asp.net core in process, maybe a better way.

Can we split the webview.native part to a standalone package and a create a new demo?

like: https://github.com/congzhangzh/desktoploveblazorweb

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant