ASP.NET Core 2.0 Empty Project


Create an empty ASP.NET Core project that doesn’t include default features i.e. an empty shell.


First create a new empty project using Visual Studio 2017

  1. File > New > Project
  2. Under “.NET Core”, select “ASP.NET Core Web Application”. Enter Name and Location. Click OK.
  3. Select “Empty”. Click OK.

Next remove the code from Program.cs and Startup.cs so that they look like below (keeping the necessary using statements):


Empty project template in Visual Studio 2017 creates a project with Program.cs and Startup.cs classes:


Just like a Console application, public static void Main() is the starting point for ASP.NET Core applications.

We’re setting up a host (WebHost) that references the server handling requests (Kestrel). This is achieved using CreateDefaultBuilder() method that configures:

  1. Kestrel: cross-platform web server
  2. Root: content root will use the web project’s root folder
  3. IIS: as the reverse proxy server
  4. Startup: points to a class that sets up configuration, services and pipeline. See next section.
  5. Configuration: adds appsettings.json and Environment Variables to IConfiguration, which is available via Dependency Injection. See next section
  6. Logging: adds a Console and Debug logging providers.

Once configured, we Build() and Run() the host, at which point the main thread is blocked and host starts listening to request from the server.

When setting up WebHostBuilder, you could set values for various settings via UseSetting() method, which takes in a key/value pair for a property. These properties include applicationName (string), contentRoot (string), detailedErrors (bool), environment (string), urls (semicolon separated list) and webroot (string). Some of these properties can also be set via extension methods on WebHostBuilder.


This class sets up the application dependency injection services and request pipeline for our application, using following methods:

  1. ConfigureServices(): add services to the service container
  2. Configure(): setup request pipeline using Middleware.

The parameters for these methods can be seen in the code listing above.

These methods are called in the same sequence as listed above. The important point to remember about the sequence in which they run is that the service container is available after ConfigureServices, i.e. in Configure() method, and not before that.

Source Code


Leave a Reply