When all code is ready, we first run dotnet ef migrations add Initial to generate Migration. Usually after this we need to run dotnet ef database update so we will have a database with _EFMigrationHistory and other empty tables. But in this project we don't need run dotnet ef database update command since we explictly call Database.Migrate() in DbContext:

using Microsoft.EntityFrameworkCore;

namespace Aspnetcore.CityInfo.Api.Entities
{
    public class AppDbContext : DbContext
    {
        public AppDbContext(DbContextOptions<AppDbContext> options)
           : base(options)
        {
            Database.Migrate();  // same as `dotnet ef database update`
        }

        public DbSet<City> Cities { get; set; }
        public DbSet<PointOfInterest> PointsOfInterest { get; set; }
    }
}

1. AppDbContextExtensions.cs
2. DbInitializer.cs

In startup.cs ConfigureServices, add below to avoid self referencing issue:

services.AddMvc().AddJsonOptions(
    options => options.SerializerSettings.ReferenceLoopHandling = Newtonsoft.Json.ReferenceLoopHandling.Ignore
);

import test/City.postman.json to postman and run test.

.Net Core default supports log information in output window. If you want to log everything in file, install NLog.Extensions.Logging.

• ViewModel and AutoMapper
• Surrogate Key
• Reverse Mapping in Post request
• Mapping source to destination in Put request
• Create Model Validation Action Filter
• SSL
• CORS
• Authentication and Authorization
• Versioning API
• REST constraints