>Hello all,
>
>So I thought it would be an easy decision to make. Where Should I go next. Angular or React. I decided to go with React for a bunch of reasons.
>
>And now here comes Blazor. I never really heard about it in the last weeks. But recently that changed.
>
>Comments?
>
>Regards

I started Blazor a few months ago with a quite substantial project, and I was impressed how fast I could be productive. So much that in this short time it surpasses VFP productivity, especially when it comes to developing new parts that were not covered with my framework. Obviously when I add code to existing features in VFP that are already covered by framework components this cannot be easily surpassed without having a framework ready in Blazor.

The following stack worked out well for me:
Blazor webassembly
EF Core
Dapper (there are some things you don't want to use Entity Framework for)
Some Javascript UI framework, for instance Blazorise or a commercial one like Telerik
ClosedXML for creating report output in Excel

I did have trouble getting Blazor Server to work, attempting to secure the web api. It works in principle, but not as I wanted it to. This would be done by scaffolding Microsoft.Identity, but it is a pain, and does not work well for me. I still need to look for a good solution. I also did not like to work with Blazor server so much and prefer Webassembly, but still not sure about how to build it really secure. For the project i had to do this was a non-issue, but obviously it's going to be important.