ReactDotNetCoreReact components as ASP.NET Core MVC views

Server-side rendered and hydrated — no Web API, no Next.js, no SPA. Keep your controllers, services, and view models; replace only the view layer.

Get Started

Architecture

GitHub

React as a view engine

return this.ReactView(model); — your existing controllers, services, and view models are untouched.

SSR + hydration

A managed Node sidecar renders React to HTML on the server; the browser hydrates the same component with the same props.

Dev mode with HMR

In Development the sidecar runs Vite — edit a .tsx and the browser hot-reloads, no rebuild.

Production-hardened

Auto free-port selection, health-gated startup, crash auto-restart, render timeouts, loopback-only sidecar, safe props escaping.

Incremental migration

Razor and React views coexist. Convert one view at a time; the rest of the app keeps working.

Two packages

ReactDotNetCore.AspNetCore (NuGet) for the engine, @react-dotnetcore/runtime (npm) for the SSR/hydration runtime.

Quick look

csharp

public IActionResult Detail(int id)
{
    var model = _userService.GetUser(id);     // unchanged domain code
    return this.ReactView<UserProfile>(model); // React instead of a Razor view
}

tsx

// Views/UserProfile.tsx
export default function UserProfile(props: UserDto) {
  return <h1>{props.name}</h1>;
}

Install both packages and you're ready:

bash

dotnet add package ReactDotNetCore.AspNetCore
npm install @react-dotnetcore/runtime react react-dom

Head to Getting Started for a full project setup.