Investigate using components with Blazor

[nmetulev]

Proposal: Investigate using components with Blazor

Description

Now that Blazor is no longer experimental, we should investigate what it would take to leverage toolkit components in Blazor.

Rationale

Blazor allows developers to use C# for their front end code (instead of JavaScript). The toolkit is intended for front end developers.

Preferred Solution

If the components 'just work' with Blazor, then the results of this investigation should be a sample in the samples folder. Otherwise, if there is work required, the result should be a write up (as part of a new issue) of what work is required to add support.

[BrianTJackett]

Are you looking to evaluate Blazor Server or Blazor WebAssembly (client)?

[nmetulev]

I'd say both. This was a community request that I've captured here, but i think it covers more than just Blazor. Things the toolkit should handle (or at least have answers for) are how do we handle defining components in Razor, supporting server side auth (behalf of flow), how do we handle interoperability between C# and JS, and more?

[dcuccia]

Thanks for posting this request. I assume the existing components should "just work" in a Blazor app. However, from a "no cliffs" perspective, first-class Blazor components that can be manipulated with C# (i.e. events and properties and intellisense) would be the most natural development experience for Blazor developers, and bridge these two rapidly growing developer communities.

[nmetulev]

I agree, the components should just work, but we have not tested them. First-class Blazor components sounds great and we'd love help from the community with the right expertise on this one

[wmgdev]

First class Blazor components would be great.

I've created a small example program which calls Graph API from Blazor Server. It handles all the auth using Microsoft.Identity.Web

https://github.com/wmgdev/BlazorGraphApi

It would be nice if I could add some example toolkit components to this.