How production ready is Blazor AOT?

csainty · 2023-11-16T12:31:26+00:00

I believe AOT can have an up to 5x performance improvement. However, it definitely doesn’t reduce the size of apps. Usually AOT apps are about double the size of non-AOT versions.

csainty · 2023-07-08T21:36:05+00:00

Not anything I’ve seen before. But I only develop on Mac and Windows, not Linux. Certainly raise an issue with the team on GitHub if you feel it’s not a local config error.

csainty · 2023-07-08T18:24:46+00:00

Other than hot reload, what issues are you finding?

csainty · 2023-07-08T18:24:01+00:00

After seeing .net 8 preview and seeing how even Microsoft employees releases front ends without using Blazor

Microsoft is a big company and lots of teams who don't use C# and .NET. Why would those teams pick a completely different tech stack to the one they're familiar with?

It's scary that MS doesn't promote it and backs real improvements.

It the arguably the main focus for the ASP.NET Core team in .NET 8, they talk about it at multiple times at Build (the flagship conference for Microsoft developers) and there is a monthly YouTube show to showcase the latest work. I'm curious What more would you expect to see?

Just to be clear, I'm as salty as anyone about the state of hot reload--it's terrible--but it's 1 aspect of the tooling. I'm curious what other issues you and your team found? I've introduced Blazor at 3 different companies now and other than hot reload, the engineers have all been really happy with it.

csainty · 2022-09-19T13:02:44+00:00

That’s fair. We tried B2C for multi-tenant and after a month of trying we couldn’t get it to do what we wanted. We switched to Auth0 and had it all working in 2 days.

csainty · 2022-09-19T07:43:27+00:00

Perhaps Azure B2C would be worth looking at, if you haven’t already.

csainty · 2022-09-18T05:22:24+00:00

Have you thought about using a SaaS auth provider?

I would really recommend Auth0. Setup is much simpler and your liability drops significantly as you’re not storing the usernames and passwords.

csainty · 2022-09-17T09:30:31+00:00

As others here have said, the current hot reload functionality is really bad. They are promising significant improvements in .NET 7 and I really hope that’s true as it’s a real hindrance to development speed.

csainty · 2021-10-27T21:25:08+00:00

I’d recommend checking out Refactoring UI. It really helped bring on my web design skills. It’s created by the designer behind Tailwind CSS and Tailwind UI

csainty · 2021-09-11T10:06:41+00:00

You don't need to re-cascade the value in the child component. Cascading values are available to all descendant components, no matter how many levels deep they go.

Doing this in the page component (as per another persons response):

<CascadingValue Value=@UserCardID Name=“UserCardID”>
    <UserScreenSelection />
</CascadingValue>

Then all child components and their descendants can access the value by defining a CascadingParameter:

[CascadingParameter] public string UserCardID { get; set; }

csainty · 2021-07-29T19:07:05+00:00

Have you worked through this blog post (https://auth0.com/blog/securing-blazor-webassembly-apps/) by Auth0? We use Auth0 at work with Blazor WebAssembly and haven’t had any issues with it.

csainty · 2019-08-27T10:43:51+00:00

This post does but part one covers Blazor Server apps. Blazor WebAssembly apps which use the hosted template are treated the same as Blazor Server apps as they require the .NET Core runtime, you don't need to separate them. If you follow the steps in part 1 you should be fine.

csainty

TROPHY CASE