This is my summary of the steps I took while experimenting with ASP.Net Core 2.1 Preview’s new React template to get a DevOps environment up and running for a new project.
To summarize the stack being used is as follows:
- ASP.Net Core 2.1 Preview
- New project with the React project template
- Visual Studio 2017 15.7 (Preview 3) [only if you want to edit the project before pushing it to the repository], you can also just use Visual Studio Code with appropriate add-ons.
- Visual Studio Team Services and Git
- Microsoft Azure App Service Web Apps
- Chocolatey package manager for the bits and pieces not yet installed
- NVM for Windows for managing Node/NPM versions
Why so bleeding edge?
Simply, the new React template included in .NET Core 2.1 Preview is a much cleaner implementation than what was available in .Net Core 2.0 in my opinion, as where the previous version had the usual Microsoft pattern of ‘customize at will’, the new template seems to keep the spirit of the React community in how it goes about deploying React as a front end project. This new ASP.Net Core React template utilizes an ASP.Net Core Web API project meant to be used for back-end heavy lifting (e.g. authentication, database etc) and keeps a true create-react-app generated application for the front-end project. I also chose to Visual Studio Team Services instead of my usual preference for Github as it provided a quick way to get both a Git repository up and running and its Build and Release features work nicely with hosting on Microsoft Azure.