Blazor Desktop plans and productization #338
Comments
|
Hi @Eilon, I watched your excellent demo here: Creating native and hybrid mobile apps with Mobile Blazor Bindings. I really enjoyed it. 😄 |
|
In .NET 6 we will build a BlazorWebView control for .NET MAUI and it will be supported on Windows and macOS. You will be able to host Blazor Web content (HTML/CSS/etc.) in a native desktop app. The rest of Mobile Blazor Bindings, such as mobile platforms, and support for native controls (for example, Button, Label, etc.) will continue in this repo and we hope to productize it in future .NET releases. |
|
@Eilon this is helpful, thank you, and it was great to see this work get some official mention at .NET Conf last week. Congrats on the project's success - can't wait to use it in production. Excuse the enthusiastic questioning, but can you say anything about:
Thanks! |
|
Why is Linux not being considered? |
|
@Kukks for .NET MAUI support we would like to run wherever .NET MAUI runs. If there is some GTK (or other) solution for MAUI, it's something we will look at. It's just about prioritization right now: we know we can deliver to Windows and macOS and they represent a huge part of the target audience. |
|
@dcuccia said:
I don't have a date; we're busy working on the official .NET 6 parts of the project right now.
There is one you can use right now in the nightly feed! I have a sample app for WPF and WinForms here: https://github.com/Eilon/MobileBlazorBindings-WindowsDesktop
Using Catalyst on macOS is the plan in .NET 6.
You can check out the closed items in the preview 6 milestone here: https://github.com/dotnet/MobileBlazorBindings/milestone/6?closed=1 There's actually quite a lot in there already, and all of it is on the nightly feed: https://docs.microsoft.com/mobile-blazor-bindings/contribute/nightly-builds |
|
I think the project naming is confusing me. "Mobile" blazor bindings in the .net 6 timeframe is only shipping in Desktop guise on Windows and macOS where it will be called Blazor Desktop hence your sample projects being in MobileBlazorBindings-WindowsDesktop. Gulp. But sadly Mobile blazor bindings isn't shipping for iOS and Android in the .net 6 timeframe. Or is it just the native controls version of Mobile blazor binding that isn't shipping, the HTML version on iOS and Android will be shipping in the .net 6 timeframe?? However at some point in the .net 6 timeframe the Mobile blazor binding native control version (still in experiment mode) will be upgraded to support .net 6. |
|
Hi @cedwards-telis I agree some of the naming is confusing! This experimental project in this repo started out as only iOS/Android, so that's why it was has "Mobile" in the name. But here's the full plan that we have:
I hope this clears a few things up! |
|
@Eilon thanks for your detailed replies (sorry for the late reply on my end). So happy to see BlazorWebView in .NET 6.0 Preview 3! https://devblogs.microsoft.com/aspnet/asp-net-core-updates-in-net-6-preview-3/ |
|
@Eilon wants to keep a way to support win7. If. Net Maui does not support win7, blazorwebview built into. Net Maui does not support win7. If so, you want to keep blazorwebview in MBB to support win7. |
|
We will ship BlazorWebView that runs on WPF and WinForms on .NET 6. Those should work fine on Windows 7. |
|
What/Where exactly is the difference between this Repo and MAUI Blazor? I've stumbled upon this Repo not too long ago and I'm somewhat confused at the moment |
|
@Z3roCoder This repo (Mobile Blazor Bindings) lets you write your UI code using Xamarin / .NET MAUI controls with the Blazor model and syntax. Basically you're writing a Xamarin / MAUI app, just with a different model. MAUI Blazor will let you host a Blazor app (so HTML and razor etc.) within a native app, specifically inside a webview wrapped in a native UI. The Blazor app itself does not use native controls, but rather web-based controls, although you can use native controls for the rest of the app outside of the webview. Those controls would be written using the normal Xamarin / MAUI model (XAML / C#). Does that make sense? |
|
@codemonkey85 So MAUI Blazor is like phonegap/cordova, whereas MBB (this repo) is properly native? If this repo is still experimental, is MAUI Blazor also? Or will it be released next month in .net 6? |
|
Mobile Blazor Binding enables building both native UI (true native UI controls) and hybrid UI (using web/HTML/CSS) in native apps. This is experimental for now. Blazor Desktop runs on .NET MAUI, WPF, and WinForms, and enables building hybrid apps. This will release next year (it got moved out of .NET 6: https://devblogs.microsoft.com/dotnet/update-on-dotnet-maui/). This will be 100% supported. |
|
So MAUI is to be released in net7 (november 22), and this repo, maybe yes maybe no. You realise it's a race between them and you? I'm betting on you, because this project is way more useful than what I've read on maui. 😄 Best of luck @Eilon! |
|
@lonix1 It's not a competition - MBB and Blazor Hybrid are solving similar needs but in different ways. There is room for both in my opinion. |
|
@lonix1 .NET MAUI will be after .NET 6 and before .NET 7. And it can't possibly be between "them and me" because I'm both of them 😄 |
|
Eilon I've heard of wearing multiple hats, but that is just ridiculous - now I have to bet on both projects!! 😄 But seriously, MBB is truly exciting stuff. V1 can't come soon enough! |
|
I hope this moves to product soon. I've watched demos and this seems very impressive. I know a lot of people love xaml but it just doesn't click with me. The blazor syntax just looks much better to me. Hope to hear more in 2022. |
|
Is this project of "Blazor Native" still active or has been abandoned and its continuation is the BlazorWebView component? @Eilon |
|
This isn't dead, but it's a low priority now. We'd love to eventually productize something like this for some future version of .NET MAUI, but that is not a commitment, and we don't have specific plans. |
I felt happy about the word "isn't dead", but what do you mean by "not a commitment"? |
|
Microsoft is not committed (yet) to ship a technology such as Mobile Blazor Bindings as an official product. It's something we're evaluating, but there is no commitment. |
|
@Eilon Is there any plan for MBB in .net 7.Is there any roadmap of it ? |
|
We don't have any update at this time. We are all busy trying to ship .NET MAUI. |
|
MobileBlazorBindings will be released in .NET MAUI, but I have a question, |
There is no browser emulation in any of these projects. The BlazorWebView control (in both Mobile Blazor Bindings, and in .NET MAUI), internally uses a platform-specific WebView control, which runs the JS code of Blazor, and also renders the HTML/CSS so that you can see the UI on the screen. All the C#/.NET code runs natively on the device/platform. Outside of BlazorWebView, Mobile Blazor Bindings uses Razor syntax to render native controls onto the screen (as opposed to HTML/CSS-based controls). In all of these cases, all of the C#/.NET code runs natively on the device, and has access to whatever features the device makes available to any other native app on the device. On iOS you can integrate with FaceID/TouchID. On Windows you can format the hard drive. On macOS you can read and write files to disk. On Android you can access SD cards. Etc. |
|
Can't wait when Blazor mobile bindings are combined with MAUI. That's the best of all worlds. |
|
@janseris I believe that Blazor Web's list virtualization features should work fine in BlazorWebView as well, which can help immensely when there are more than a few hundred/thousand rows of data to display. More info here: https://docs.microsoft.com/aspnet/core/blazor/components/virtualization?view=aspnetcore-6.0 But, either way, I am starting to spend some time to incorporate @Dreamescaper 's amazing work on MAUI Blazor Bindings back into this repo. You can check out their project here, if you haven't seen it yet: https://github.com/Dreamescaper/BlazorBindings.Maui |
|
@Eilon that makes me incredibly happy. I’m learning XAML, but I’m sure I can’t be the only one who prefers Blazor’s binding model, among other things. |
You can't expect this being ever completed when there are like only 5 people programming both MAUI and this. They would need whole life to complete both platforms which it now almost takes for MAUI. Supposed to be shipped in ,NET 6 (November 2021) and is not working properly even 9 months later when officially relased in June 2022. |
|
dotnet Blazor MAUI, will have support for Apple Watch? |
|
@nowlights that question should probably go to the https://github.com/dotnet/maui repo, but I believe the answer is no, not for now. Please refer to an earlier discussion on this: dotnet/maui#1144 and you can add your thoughts there. |
|
Hi @Eilon, since v7 was released in November, and MAUI is now a thing, is there any change in this project's status? Is it still purely "experimental", or is there interest in moving it forward? Because to repeat what was said umpteen times above, this library is an absolute gamechanger. |
They working on BlazorBindings.MAUI |
|
Thanks, I know about that project, but I with the utmost respect to its author, I'm waiting for something official from Microsoft. I hope Eilon can update us now that v7 is out. |
|
I hope that some form of this library become a real thing. I'm using MAUI blazor app and it a breeze to develop with. Real native "Blazor" would be awesome! |
I've been waiting for an update on this as well for a while now. I'm surprised they aren't pushing this along with all the new blazor stuff. This would be indeed a game changer, especially for enterprise mobile development in MAUI. Xaml is something of the past and an unified syntax will be so much better. Tagging @SteveSandersonMS |
|
What happened to this project? Microsoft abandoned it. |
Hello fans of Mobile Blazor Bindings!
As some of you may know, we are working on productizing some key components of Mobile Blazor Bindings and will release them later this year (2021) as part of .NET 6. Our main focus will be on desktop support for Windows and macOS, but we are looking to enable authoring apps on as many platforms as possible.
What does "productization" mean? That means that the features that ship in .NET 6 will be fully supported and not experimental. The features will abide by all the same benefits and policies of anything in .NET 6, such as compatibility, breaking changes, paid support, patch releases, etc.
The work for this will mostly be done in the ASP.NET Core GitHub repo because that's where the rest of Blazor is and much of the code is shared.
To get a glimpse of some of the features and issues we're looking at you can query issues using the
feature-blazor-desktoplabel on the ASP.NET Core repo: https://github.com/dotnet/aspnetcore/labels/feature-blazor-desktopIf you have thoughts or comments on any of those issues, please add them to the issues!
Thanks,
Eilon Lipton
The text was updated successfully, but these errors were encountered: