Blazor Desktop plans and productization

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-desktop label on the ASP.NET Core repo: https://github.com/dotnet/aspnetcore/labels/feature-blazor-desktop

If you have thoughts or comments on any of those issues, please add them to the issues!

Thanks, Eilon Lipton

[Eilon]

@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

[codemonkey85]

@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.