Solution overview

The first thing that catches the eye is that, as we’ve already mentioned, the layout of a standard ASP.NET Core solution is quite different from what it used to be in ASP.NET 5 and earlier versions. The most notable thing is that we have two different projects – one for Angular (healthcheck.client) and one for the ASP.NET Core Web API (HealthCheck.Server) – that start together and need to interact with each other. If you have previous “classic” ASP.NET single-project experience, you may find such an approach quite different from what you are used to working with.

The best thing about the new approach is that we’re instantly able to distinguish the ASP.NET back-end part from the Angular front-end part, which could be troublesome with the previous single-project experience, when the two stacks were often intertwined.

Let’s quickly review their overall structure to better understand how each one of them works...