ASP.NET Core TypeScript
Part of my ASP.NET Core recipe series: compiling TypeScript as part of the project so the frontend gets types too.
13 articles in the notebook
Part of my ASP.NET Core recipe series: compiling TypeScript as part of the project so the frontend gets types too.
Part of my ASP.NET Core recipe series: using the built-in memory cache for data you don't want to fetch on every request.
Part of my ASP.NET Core recipe series: enabling response caching so identical requests are served without re-executing the pipeline.
Part of my ASP.NET Core recipe series: wiring up AutoMapper to map between entities and view/API models without hand-written copy code.
Part of my ASP.NET Core recipe series: moving EF Core into its own project so the data layer stays separated from the web application.
Part of my ASP.NET Core recipe series: exposing your API with Swagger UI so it documents and exercises itself.
Part of my ASP.NET Core recipe series: adding API versioning so /api/v1/ and /api/v2/ can coexist while clients migrate at their own pace.
Part of my ASP.NET Core recipe series: carving out an /api/-area in an MVC project so pages and API endpoints live cleanly side by side.
Part of my ASP.NET Core recipe series: binding appsettings.json to typed config classes so settings are managed code instead of magic strings.
Part of my ASP.NET Core recipe series: replacing the default logging with Serilog for structured logs with proper sinks.
The opening recipe in my ASP.NET Core series: setting up a clean MVC project as the foundation the rest of the recipes build on.
Bulk-importing users through Identity Framework 3 kept failing with disposed-object and modified-collection errors. The culprit: async void. Change to async Task and await properly — code included.
Visual Studio 2015 has no GUI support for Areas in ASP.Net 5 yet. The workaround is simple: create the folder structure manually and add an area route in Startup.cs — shown here.