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
I am developing a SPA webapp that shares its backend services with a WPF application. It is being suggested to make a single platform out of these 2 apps but without sacrificing any of them, i.e without changing the webapp to WPF and without changing the WPF and making it a webapp, simply because the features each platform provides are hard to duplicate in the other.
one of the solutions being put forth is to use WebView2 in .Net to run the webapp inside the native app.
I have no clue what the limitations of Webview2 are, but other than the hell of non existent development tools for it (thinking developer view, browser debugger etc...) what could possibly make this a horrible idea?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I am developing a SPA webapp that shares its backend services with a WPF application. It is being suggested to make a single platform out of these 2 apps but without sacrificing any of them, i.e without changing the webapp to WPF and without changing the WPF and making it a webapp, simply because the features each platform provides are hard to duplicate in the other.
one of the solutions being put forth is to use WebView2 in .Net to run the webapp inside the native app.
I have no clue what the limitations of Webview2 are, but other than the hell of non existent development tools for it (thinking developer view, browser debugger etc...) what could possibly make this a horrible idea?
Beta Was this translation helpful? Give feedback.
All reactions