GraphicsControls VS ASP.NET Core

If you need this scenario, you can take a look at Maui.Graphics.Controls, and see if that fits your needs, right it's an experimental idea.

And as Microsoft mentioned in the podcast, there are also implementations that use drawn controls, but those are not the standard ones and must be specifically downloaded separately by the developer. For example, https://github.com/dotnet/Microsoft.Maui.Graphics.Controls - " a .NET MAUI experiment that offers cross-platform, pixel-perfect, drawn controls"

To note, Maui does theoretically allow pixel perfect rendering with it's renderer architecture. An experiment called Microsoft.Maui.Graphics.Controls does that through Maui.Graphics and can be a possible solution for targeting Linux. Though yeah it's an experiment overall than sometimes supported at the moment.

If however you're looking for custom controls, i've found very little describing how to go around making your own custom control. There is one repo on github made by one of the team: https://github.com/dotnet/Microsoft.Maui.Graphics.Controls

Linux is experimentally supported if you use Microsoft.Maui.Graphics.Controls

The MS team have an experiment for Maui drawn controls: https://github.com/dotnet/Microsoft.Maui.Graphics.Controls I'm kind of hoping it becomes a full blown Maui feature at some point down the line 😁

Yes. Maui.Control.Graphics is a feature in that lets you create your UI pixel-perfect across platform. They even let you choose the design language to use (Material, Cupertino, and Fluent). Right now the controls are still few and very limited, not to mention that this feature is still experimental. They are also drawn using the platforms rendering API (explanation here)

It looks really cool tbh, seen a couple of videos. You can check it out here if you're interested: https://github.com/dotnet/Microsoft.Maui.Graphics.Controls

It doesn't support web. The most promising components at the moment to make this happen are: - https://github.com/dotnet/GraphicsControls . First they will need to get this working with normal platforms. - https://github.com/dotnet/Microsoft.Maui.Graphics . A dependency of the above library. Web code exists here but is not yet functional. - Blazor. In order to deploy usable Blazor wasm apps they need to get AOT support working: https://github.com/dotnet/aspnetcore/issues/5466 (Note the blazor you read about that is connected with MAUI is just another style of writing MAUI apps and doesn't allow MAUI apps to run on the web.)

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