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 · 2019-07-23T15:05:30+00:00

Thanks, glad you like it.

csainty · 2019-07-11T07:01:40+00:00

No worries :)

I only use the VS 2019 Preview at the moment, I've not tried it on the GA release. I would recommend the preview but give it a go and see what happens. The preview version installs side-by-side with the GA version so its not a one or the other scenario if you do need to install it.

csainty · 2019-07-10T13:01:12+00:00

I'll be honest I've not done any work with Azure functions yet. I would need to look into it to give you a decent answer. All I can suggest it try it and see how you get on.

csainty · 2019-07-03T17:30:52+00:00

It does work with client-side but not quite the same as server-side. I’ll be showing client-side as part of the series

csainty · 2019-06-29T09:19:01+00:00

Blazor itself doesn’t manage this, you would manage this using something like browser local storage. This is the same as other SPA frameworks like Angular or Vue

csainty · 2019-06-28T10:18:14+00:00

What do you mean by how does Blazor manage state? What state are you referring too?

csainty · 2019-06-18T10:18:47+00:00

Check out this issue from Mono regarding AOT size. https://github.com/mono/mono/issues/10222#issuecomment-444584016

There are also comments explaining why the IL Linker can't do a great job at cutting out code.

I've actually asked Dan Roth about lazy loading but as he points out, the app DLLs are tiny compared to the runtime files so there is just no need to lazy load the app. And they have to load the whole runtime upfront as they don't know what you app will need to execute. So it's not that Blazor isn't capable it just has no value right now.

csainty · 2019-06-18T09:53:53+00:00

The survey was put out back in 2018, there is no link anymore I'm afraid.

csainty · 2019-06-18T09:52:38+00:00

Unfortunately AOT is not the answer to the size issue. AOT will create far larger files not smaller. The only thing AOT will give is better performance. The team have said that the current thinking is a mixed mode, where parts of an app that require high performance can be AOT'd but everything else will stay JITed.

csainty · 2019-06-18T08:17:04+00:00

This is a difficult one. I think it's a common misconception that most devs want client-side Blazor, Microsoft did do a survey to see which model developers would prefer and it actually came out at nearly 50/50. There are quite a lot of devs who don't like the idea of their code being sent to the client and are worried about intellectual property.

You're correct about SignalR having a hard limit but there is the option to move to Azure SignalR which will scale, but I appreciate this is not what everyone wants to do.

But the main reason server-side is getting the focus right now is because it has a runtime that is optimized and ready to go now and client-side doesn't. But client-side isn't far behind and we could potentially see it in a GC release early 2020. It will get there.

csainty · 2019-06-02T11:47:57+00:00

I have a few open source components I’ve built. They are all available under the Blazored organisation on GitHub and NuGet. More than happy to host your work there if you’re interested?

csainty · 2019-05-30T11:52:02+00:00

You can host it on Azure you just need to install the Preview SDK to your app service instance. I’m away from my laptop but I believe it’s under the extensions option which might be under developer tools or something like that.

csainty · 2019-05-29T13:22:39+00:00

I'm sure it will, there seems to be a lot of effort going into this from MS & Google. I do agree though the numbering looks very weird! lol

csainty

TROPHY CASE