ASP.NET Core VS MobileBlazorBindings

> Just .GetAwaiter().GetResult() it.

That won’t work with various synchronization contexts, where doing this would cause a deadlock. There’s not much fun in trying to debug such issues.

And now that various libraries only provide async api, or worse an non-async version wrapping the async one with . GetAwaiter().GetResult(), you’ll be in for a treat updating your dependencies.

Async all the way is the answer, although various frameworks still don’t offer async hooks. Recently I ran into this for example trying to write an async validator in blazor, but that’s not possible and you have to work around it [1].

C# 5 introduced async/await almost 12 years ago. And we’re still not “async all the way”.

[1]: https://github.com/dotnet/aspnetcore/issues/40244

This approach to organizing middleware enhances code readability, maintainability, and reusability. By following this encapsulation pattern, you're adhering to best practices in ASP.NET Core development, ensuring your application remains well-organized and scalable.

🌟.NET 9 Preview 2 ➡️.NET 9 Preview 2 Discussion ➡️ASP.NET Core updates in .NET 9 Preview 2 ➡️ASP.NET Core updates in .NET 9 Preview 2 Release Notes ➡️EF Core updates in .NET 9 Preview 2 ➡️.NET Aspire preview 4 - .NET Aspire

https://github.com/dotnet/aspnetcore/issues/50643

Even if you look at Microsoft’s by far most popular GitHub project, they’re still only half as big as SupaBase. If you believe “the SupaBase story”, SupaBase grew and became twice as large as Microsoft in 3 years. Below is their likes over time if you’re curious, together with a couple of additional “too good to be true” Silicon Valley projects.

https://github.com/dotnet/aspnetcore/issues/10117

To achieve these objectives, we will take inspiration from ASP.NET Core Identity's PasswordHasher class. It incorporates a concept of hash versioning, allowing only the number of iterations to be modified.

yes I watched several courses, may be aim not getting clearly. but i worked with asp.net which uses http call and firebase cloud function also which uses socket connection, for socket connection its makes sense to use observable bcoz there streams of data we can observe once the connection establish ,but for http it need to be call every time.

It's difficult to imagine. But if the rumour has any merit, perhaps it simply means that there will be a push to consolidate on some blazor tech using stuff like https://github.com/dotnet/MobileBlazorBindings

There's Blazor Mobile Bindings but it's essentially experimental at the moment and isn't exactly active. From playing around with it though, it is pretty neat as you get the Blazor programming model but with native controls.

The benefit at least with the approach instead of embedding Avalonia inside Maui is you could potentially use non xaml frameworks for ui as long as they support Maui as a target. Stuff like Comet or Blazor mobile bindings would be possible aside from xaml. Especially if they're coming from Blazor web or code based ui frameworks like flutter which makes it appealing.

This is one reason I'd really love for them to push through on making alternatives to XAML like Blazor mobile bindings.

I'd say Blazor mobile bindings is also pretty interesting imo, unlike Hybrid it doesn't use Html and uses MAUI controls directly but still keeps the Blazor programming style and still uses razor to tie in C# and components.

Oleksandr has been contributing to the official experiment project, and singlehandedly updated it to support .NET MAUI. He even now has documentation on his fork.

I really hope Blazor Mobile Bindings takes off imo. I still care for native controls and if Mobile bindings does become a valid target, then you'll have an alternative to XAML when writing native components but using Razor syntax (which imo is less verbose). It'll be like how React does it (which is still pretty popular) where you have React web and also React Native which uses the platform's native controls underneath. Both aren't exactly the same but since the framework is similar (React, Blazor) it should be easy to swap between the two.

Yeah I really hope they'll productize Blazor Mobile Bindings (currently experimental), it's essentially using Xaml controls via Razor as the markup format instead and can use C# expressions (so less need for converters).

For example, in Android there's this file: https://github.com/dotnet/MobileBlazorBindings/blob/main/templates/BlazorHybrid-app/NewApp.Android/wwwroot/index.html

It means you can use Blazor's syntax to write MAUI apps, as an alternative to XML-like XAML syntax.