In August 2019, the Microsoft ASP.NET Core team announced that the Microsoft.AspNetCore.SpaServices and Microsoft.AspNetCore.NodeServices are obsoleted. Originally, these packages were used to integrate ASP.NET Core with frontend frameworks and libraries like Angular and React and were part of the Visual
Lean ASP NET Core 2.1 – React forms, validation and Web API integration
This post is part of a multi-post series: Lean ASP.NET Core 2.1 – manually setup a Razor Pages project with Bootstrap, NPM and webpack Lean ASP.NET Core 2.1 – add a React application to an existing Razor Pages application Lean
Lean ASP.NET Core 2.1 – add a React application to an existing Razor Pages application
This post is part of a multi-post series: Lean ASP.NET Core 2.1 – manually setup a Razor Pages project with Bootstrap, NPM and webpack Lean ASP.NET Core 2.1 – add a React application to an existing Razor Pages application (this
Lean ASP.NET Core 2.1 – manually setup a Razor Pages project with Bootstrap, NPM and webpack
This post is part of a multi-post series: Lean ASP.NET Core 2.1 – manually setup a Razor Pages project with Bootstrap, NPM and webpack (this post) Lean ASP.NET Core 2.1 – add a React application to an existing Razor Pages
Building the minimal ASP.NET Core MVC app with NPM and webpack
Update: this post is written using ASP.NET Core 1.1. With ASP.NET Core 2.0, things have gotten easier. See the updated version of this post for ASP.NET Core 2.0. Recently, I was building a ASP.NET Core MVC app. Everything went smooth,