This is a solution template that extends the "React and ASP.NET Core (Preview)" .NET 7 template that comes with Visual Studio.

That template sets up the client side under the nice new esproj project type which makes doing the front end from full Visual Studio a bit friendlier.

The front end is based on Create React App with the Webpack Dev Server proxy configured for forward requests on to the .NET Web API

Open the solution in Visual Studio, set TemplateApp.FrontEnd and TemplateApp.WebApi as your startup projects and click start.

Before

• React (JavaScript)
• Rest API (Web API)

After

• React (TypeScript)
• React Router
• GraphQL API (Apollo client + Codegen + HotCocolate server)
• Entity Framework

Where as the template at the moment just has a plain page that gets the list of weather forecasts.

The UI from the template Blazor app has been added along with client side routing to switch between views.

One of the tricky parts I came across was that in the template Blazor app it showcases the CSS isolation features built into Blazor/Razor. Converting this wasn't entierly straightforward.

With Blazor CSS isolation if you follow the naming convention

├── MyComponent.razor
├── MyComponent.razor.css

The framework will isolate the css in that file so that it only applies to that component. The way this works is for example in MainLayout.razor is each tag will have a unique attribute for that component added to it in the final compiled markup E.G.

- <div class="page">
-    ...
+ <div class="page" b-45rkf8v3vv="">
+    ...

Then in the corresponding MainLayout.css its content will get altered in the final CSS bundle like so

- .page { 
-   ...
+ .page[b-45rkf8v3vv] { 
+   ...

Create React App has built in support for something similar - CSS modules. Again there is a naming convention E.G.

├── MyComponent.tsx
├── MyComponent.module.css

Then a slightly different syntax for importing / applying styles in your component. Basically you can import your styles from the stylesheet into an object in your component and then use them like this

return <button className={styles.error}>Error Button</button>;

Which will render as something like

<button class="Button_error_ax7yz">Error Button</button>

However because you are no longer applying the original class name it doesn't play so nicely when you are overriding vendor supplied styles, E.G. Bootstrap's btn class would get replaced and the original style would no longer apply.

The quick fix for this I applied was the CssModuleNameComposer class which will take a list of unadulterated class names and return the className string including any CSS module hashes that have been defined for that class name.

Example Input: ["page"]

Example Output "page Layout_page__M3sKN"

Here are the resources I used to help figure this out:

Full-Stack React and .NET with GraphQL

ASP.NET Core Blazor CSS isolation

Create React App - Adding a CSS Modules Stylesheet