Getting Started on ASP.NET Core

Getting started with ReactJS.NET on ASP.NET Core requires a few more steps compared to previous versions of ASP.NET and MVC. If you want a step-by-step guide on configuring a brand new site, see the ReactJS.NET tutorial for ASP.NET Core.

ReactJS.NET requires Visual Studio 2015 and ASP.NET Core RTM (final release). It is recommended to use .NET Framework, but ReactJS.NET also works with .NET Core.

Install the React.AspNet package through NuGet. After the package is installed, ReactJS.NET needs to be initialised in your Startup.cs file (unfortunately this can not be done automatically like in previous versions of ASP.NET with WebActivator). At the top of the file, add:

using Microsoft.AspNetCore.Http;
using React.AspNet;

Directly above:

// Add framework services.


services.AddSingleton<IHttpContextAccessor, HttpContextAccessor>();

Directly above:



// Initialise ReactJS.NET. Must be before static files.
app.UseReact(config =>
  // If you want to use server-side rendering of React components,
  // add all the necessary JavaScript files here. This includes
  // your components as well as all of their dependencies.
  // See for more information. Example:
  //    .AddScript("~/Scripts/First.jsx")
  //    .AddScript("~/Scripts/Second.jsx");

  // If you use an external build too (for example, Babel, Webpack,
  // Browserify or Gulp), you can improve performance by disabling
  // ReactJS.NET's version of Babel and loading the pre-transpiled
  // scripts. Example:
  //    .SetLoadBabel(false)
  //    .AddScriptWithoutTransform("~/Scripts/bundle.server.js");

Finally, add this to Views\_ViewImports.cshtml (or create it if it doesn't exist):

@using React.AspNet

Once ReactJS.NET has been configured, you will be able to use on-the-fly JSX to JavaScript compilation and server-side rendering.