From the course: .NET 9 Maui: Enhanced Features for Cross-Platform Development
Unlock this course with a free trial
Join today to access over 24,900 courses taught by industry experts.
BlazorWebView behavior changes
From the course: .NET 9 Maui: Enhanced Features for Cross-Platform Development
BlazorWebView behavior changes
- [Instructor] There have been a few changes to the BlazorWebView in .NET 9 nine. The first is done for iOS and Mac OS, but it impacts all platforms. It changes the default IP address that is used and prior versions of .NET, the BlazorWebView hosted it's content at the IP of 0.0.0.0. However, as of iOS versions 18 and Mac OS 15, this no longer works. In .NET 9, the default hosting location is 0.0.0.1. Any older BlazorWebView application that has not been updated to .NET 9 may not work on iOS 18 and above and Mac OS 15 and above because of this. The new default address of 0.0.0.1 will work and it will also work on the previous versions of those platforms. However, if the old address is needed for whatever reason, the application can be set to use the old 0.0.0.0 address. We will look at that in a bit. I have included two links to the issues that cause this change for your interest. The second change is Android only. The default behavior to run the dispose for the WebView manager is now…
Contents
-
-
-
(Locked)
What is this update all about?3m 45s
-
HybridWebView control5m 27s
-
(Locked)
HybridWebView calling JavaScript from C#6m 44s
-
HybridWebView calling JavaScript and calling C#6m 16s
-
(Locked)
Titlebar for Windows5m
-
(Locked)
Titlebar for Windows customizations5m 33s
-
(Locked)
BlazorWebView behavior changes4m 58s
-
(Locked)
CollectionView/CarouselView for Apple devices5m 50s
-
(Locked)
SoftKeyboard input2m 59s
-
(Locked)
Text justification2m 47s
-
(Locked)
TimePicker TimeSelected event5m 22s
-
(Locked)
WebView ProcessTerminated event5m 47s
-
(Locked)
-
-
-
-
-