Blazor

[torhovland]

Codebase in progress:

https://github.com/torhovland/blazor-realworld-example-app
If you'd like to help out, you're welcome!

Demo:

https://blazor-realworld.azurewebsites.net

[stavroskasidis]

Is this dead ? Can someone else give it a go ?

[burke166]

Try this: https://github.com/burke166/blazor-client-side-realworld-example-app

I can't fork directly from the original because I created a fork for the server-side app.

There are also a lot of changes to Blazor from 0.3 to now, so the structure is somewhat different.

[HugoDoyon]

Guys: Why the Blazer.net demo app taking so long to load compare to React demo (see here https://github.com/gothinkster/realworld)?

Is it Blazor.net "Server" version that create this "loading..." delay?

Hoping C# will be able to challenge React or Angular speed one day!

[coman3]

@HugoDoyon, have a close look at the network tab in chrome. You'll see that the app is just HUGE compared as it needs to download the mono WASM runtime...

[HugoDoyon]

Indeed Mono WASM is Massive 1.72MB! Microsoft can do much better than that!

[rohanbojja]

@HugoDoyon Indeed, perhaps in the near future. They addressed this in one of the Blazor sessions.

[JoeyMckenzie]

Following up on this. From the looks of the two previously linked repos in this thread, it seems that both projects have been somewhat abandoned. I'd like to offer up my implementation using the latest version of .NET Core:

Repo: https://github.com/joey32793/BlazorConduit
Demo: https://blazor-conduit.netlify.app/

While I'm positive there's still some work to do (currently at v1.0.0-mvp), anyone is welcome to pitch in. I've completed all the required workflows and added a few cypress tests, but I would like to eventually add bUnit tests (mostly for pipeline build reassurance) if anyone is interested in a good first issue. CI/CD is hooked up through Azure DevOps, and I'll be continually working on this as time permits.

[geromegrignon]

Hello we are currently moving all work in progress to Github Discussions.
I'll close this issue by now, you can find instruction to open a discussion there : #633

Thanks for your contribution !