Obuka
Modul
Remotely debug ASP.NET Core apps hosted on Azure App Service using Visual Studio - Training
Hands-on training to deploy and remotely debug your ASP.NET Core apps on Azure App Service directly using Visual Studio 2022.
Ovaj preglednik više nije podržan.
Prijeđite na Microsoft Edge, gdje vas čekaju najnovije značajke, sigurnosna ažuriranja i tehnička podrška.
To use Microsoft Edge DevTools to debug a WebView2 WinUI 2 (UWP) app, use remote debugging. Remote debugging is necessary for WebView2 WinUI 2 (UWP) apps because currently, the built-in DevTools can't be launched inside a store-signed WebView2 WinUI 2 (UWP) app.
Attach Microsoft Edge DevTools remotely to an Xbox WebView2 WinUI 2 (UWP) app as follows:
In Microsoft Edge, go to edge://inspect
. The Inspect with Edge Developer Tools page opens:
Enable Developer Mode on Xbox. See Xbox One Developer Mode activation.
In Microsoft Edge, go to https://<System IP>:11443
, where <System IP>
is replaced by your Xbox System OS IP. The Confirm security settings page is displayed, in the Windows Device Portal tab:
Click the Continue with an unsecured connection button. An SSL cert error appears, NET::ERR__CERT_AUTHORITY_INVALID:
Click the Advanced button. A message is displayed, "The server couldn't prove ...":
Click the Continue to <System IP>
(unsafe) link, where <System IP>
is replaced by your Xbox System OS IP. Xbox Device Portal opens:
Go to https://<System IP>:11443/config/rootcertificate
, where <System IP>
is replaced by your Xbox System OS IP. This downloads a rootcertificate.cer
file:
Open the downloaded rootcertificate.cer
file. A security warning dialog box opens:
Click the Open button. A Certificate dialog opens:
Click the Install Certificate button. A Welcome to the Certificate Import Wizard dialog opens:
Select the Current User option button, and then click the Next button. The Certificate Import Wizard opens:
Select the option Place all certificates in the following store, click the Browse button, and then select Trusted Root Certification Authorities.
Click the Next button. A Security Warning dialog opens:
Click the Yes button.
Restart Microsoft Edge.
Go to https://<System IP>:11443
, where <System IP>
is replaced by your Xbox System OS IP, and verify that the connection is indicated as secure (that is, an HTTPS URL):
In your app project, set the following variable, to configure your WebView2 WinUI 2 (UWP) app for remote debugging.
To enable remote debugging, an environment variable must be set in your project. This variable must be set before creating the CoreWebView2
instance, and before either setting the WebView2.Source
property or calling the WebView2.EnsureCoreWebView2Async
method.
"WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS", "--enable-features=msEdgeDevToolsWdpRemoteDebugging"
For example, if you're using the WebView2 Sample UWP app, you can set the environment variable by adding the following line in the Browser.xaml.cs
file:
Environment.SetEnvironmentVariable("WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS", "--enable-features=msEdgeDevToolsWdpRemoteDebugging");
The line is numbered 33 in this screenshot, in the Browser()
constructor, below an #endif
that wraps an existing SetEnvironmentVariable
statement:
Deploy your app to your Xbox using Xbox Device Portal
and launch your app.
Go to edge://inspect
.
In the Connect to a remote Windows device text box, enter https://<System IP>:11443
, where <System IP>
is replaced by your Xbox System OS IP, and then click the Connect to Device button.
Verify that you can successfully connect, so that your debuggable WebView2 control, named Edge, is listed under your machine name:
At the bottom of the Edge WebView2 control entry, click the inspect link. Microsoft Edge DevTools opens for the WebView2 control:
Now you can use Microsoft Edge DevTools to inspect and debug the WebView2 control in your Xbox WebView2 WinUI 2 (UWP) app.
Obuka
Modul
Remotely debug ASP.NET Core apps hosted on Azure App Service using Visual Studio - Training
Hands-on training to deploy and remotely debug your ASP.NET Core apps on Azure App Service directly using Visual Studio 2022.