As soon as we install the .NET Core Windows Server Hosting bundle, we'll be able to configure our IIS instance to host our application.

From the IIS Manager interface, right click on Sites and choose the Add New Website option. Name it with your solution name, project name, domain name, or anything you like, depending on the naming convention we chose to adopt for our IIS website entries. In this book example, we went with www.testmakerfree.com, since that's the domain we were to use.

By looking at the read-only textbox to the immediate right, we can see that a new Application Pool will also be created with that same name. Take a mental note of it, as we'll need to configure it soon enough.

Set the physical path of the Content Directory to the folder we targeted for FTP publishing.

In our example, it should be something like C:inetpubTestMakerFree, assuming that the FTP root for the web admin user points to C:inetpub. Just ensure that you target the application's root folder, not the wwwroot subdirectory.

As for the bindings, either choose a specific IP address or leave the All Unassigned option and choose a Host name that is already configured to redirect to our web server via DNS; in our example, since we already set up the www.testmakerfree.com domain name with a DNS redirect to our web server's public IP address, we'll just use that:

Before clicking on the OK button, ensure that the Start Website immediately option is checked, so the website will immediately be available.