This repository contains the code samples for ASP.NET Core in Action, Second Edition

No code samples

• WebApplication1 - A sample web application, based on the Visual Studio Razor Pages template
• ErrorHandler - A sample application demonstrating the built-in error handling. The home page (Pages/Index.cshtml.cs throws an exception when executed.

• CreatingAHoldingPage - 3.2.1 Simple pipeline scenario 1: A holding page
• CreatingAStaticFileWebsite - 3.2.2 Simple pipeline scenario 2: Handling static files
• SimpleRazorPagesApplication - 3.2.3 Simple pipeline scenario 3: A Razor Pages application
• SimpleRazorPagesApplicationAndHoldingPage - 3.2.3 Simple pipeline scenario 3: A Razor Pages web application + a holding page for "/"
• DeveloperExceptionPage - 3.3.1 Viewing exceptions in development: the DeveloperExceptionPage
• ExceptionHandlerMiddleware - 3.3.2 Handling exceptions in production: the ExceptionHandlerMiddleware
• StatusCodePages - 3.3.3 Handling other errors: the StatusCodePagesMiddleware
• StatusCodePagesWithRexecute - 3.3.3 Handling other errors: the StatusCodePagesMiddleware. Reexecuting the pipeline to create custom status code pages

• ATypicalRazorPage - 4.1.1 Exploring a Simple Razor Page
• AddingRazorPagesToEmptyProject - 4.1.4 Adding Razor Pages to an "Empty" web application template
• ConvertingToMvc - 4.2 An MVC application, with separate Model, View, and Controller files
• PageHandlers - 4.3 Using different Razor Page handlers to handle different HTTP verbs (GET and POST)

• RoutingExamples - Multiple examples of routing. In particular, see Search.cshtml, Products.cshtml, and ProductDetails/Index.cshtml. Index.cshtml includes links demonstrating route parameters
• ChangingConventions - 5.7. Customizing the URLs using conventions. See Startup.cs

• ToDoList - Basic application demonstrating the application in Figure 6.1
• ExampleBinding_EditProduct - Binding a custom class using Model Binding
• ExampleBinding_Calculator - Binding a custom class using Model Binding
• SimpleCurrencyConverterBindings - Model binding simple properties. Demonstrates Table 6.1, binding to route parameters, form parameters and the querystring
• ListBinding - Model binding to collections, as shown in Figure 6.5
• ValidatingWithDataAnnotations - A dummy checkout page, demonstrating Model validation using various DataAnnotations. Also shows POST-REDIRECT-GET
• CurrencyConverter - A dummy currency converter application. Demonstrates model binding, DataAnnotations, and a custom validation attribute
• RazorPageFormLayout - Organising a Razor Page for model binding, as in section 6.4

• ManageUsers - Display a list of users, and allow adding new users, as shown in figure 7.3
• DynamicHtml - Example of creating dynamic HTML by using C# in Razor templates.
• ToDoList - Example of writing model values to HTML in Razor templates, as shown in section 7.2
• NestedLayouts - Demonstrates using a nested layout, where a two column layout, _TwoColumn.cshtml is nested in _Layout.cshtml.
• PartialViews - Demonstrates extracting common code into a partial view, as in section 7.4.3. Also shows adding additional namespace to _ViewImports for PartialViews.Models namespace.
• DefaultMVCProject - Default MVC template, showing the default conventions for finding a view. Also shows how you can specify the template to Render - the HomeController specifies alternative view to render at the URL /Home/IndexThatRendersPrivacy

• CurrencyConverter - A demo currency converter application using TagHelpers to generate form elements.
• TagHelpers - Demonstrates the input types generated for various property types and DataAnnotations, as described table 8.1.
• SelectLists - Generating a variety of select lists, as shown in section 8.2.4
• EnvironmentTag - Using the environment tag to conditionally render content, as shown in section 8.5

• BlazorWebAssemblyProject - A basic Blazor WebAssembly web application, as shown in Figure 9.1, created using the Blazor WebAssembly template. Follow the instructions at https://docs.microsoft.com/en-gb/aspnet/core/blazor/get-started to try it for yourself.
• DefaultWebApiProject - The default Web API project, created using the Visual Studio API template, as in section 9.2.
• BasicWebApiProject - A basic Web API project, returning a list of fruit, as demonstrated in section 9.2.
• UsingApiControllerAttribute - A project containing 2 controllers, demonstrating the additional code required if you don't use the [ApiController] attribute, as in section 9.5.
• ProblemDetailsExample - A simple API controller that demonstrates automatically returning a ValidationProblemDetails object when the binding model (the myValue route parameter) is empty.
• CarsWebApi - A Web API controller that demonstrates generating various different response types. Is configured to allow XML output in Startup.cs Use https://www.getpostman.com to make requests to the API. Also configured to use the Newtonsoft.Json formatter instead of the System.Text.Json formatter.

• SendingAnEmailWithoutDI - An example demonstrating a use case where you want to send an email when a user registers. The EmailSender class is created in code using new as shown in section 10.1.1 and Listing 10.3.
• SendingAnEmailWithDI - A refactoring of the SendingAnEmailWithoutDI project to use DI, showing how the UserController has been simplified.
• InjectingMultipleImplementations - Example demonstrating the behaviour when registering multiple instances of a service, as in section 10.2.4. Click the buttons shown on the home page and observe the console output to see the effect of the DI configuration
• LifetimeExamples - The effect of lifetime on DI. For details, see section 10.3 - the project broadly follows this outline, with slightly different naming to allow registering all the services in a single project.

• ReplacingDefaultConfigProviders - Demonstrating how you can replace the configuration providers added in CreateDefaultBuilder, as shown in section 11.3.1.
• StoreViewerApplication - A simple application that uses IOptions<> and strongly typed settings to bind configuration to POCOs. Optionally uses Google Maps to demonstrate loading settings from multiple sources. Follow the documentation from Google to obtain an API key.
• DesigningForAutomaticBinding - Demonstrating how to create strongly typed settings that can be bound to configuration, and the limitations, as shown in section 11.4.3.
• LifetimeExamples - Demonstrates how to overwrite values based on the environment. In particular, observe how list values are overwritten.

• InstallEFCore - Demonstrating how to install EF Core, as shown in section 12.2. Starts from the Default Web App template from Visual Studio and installs the EF Core packages, adds the Recipe and Ingredient entities, configures the AppDbContext, and registers EF Core with the DI container. Configured by default for Local DB, but demonstrates how to configure the application for SQLite instead.
• Migrate_LocalDb - The same code as InstallEfCore, but with migrations added using the dotnet-ef global tool. Migrations generated for Local DB.
• Migrate_SQLite - The same as Migrate_LocalDb but configured for SQLite, and with SQLite-specific migrations generated by the dotnet-ef global tool.
• RecipeApplication_LocalDb - The final Razor Page application, using the Local DB database provider.
• RecipeApplication_SQLite - The final Razor Page application, using the SQLite database provider.

• FilterPipelineExample - A sample application with a single API Controller and a single Razor Page that contains one of each filter, and logs when the filter runs. Each filter contains commented out code to short-circuit the pipeline. Uncomment the code from each filter in turn to see the effect.
• RecipeApplication - The RecipeApplication from chapter 12 plus two API controllers. The NoApiController includes the code from listing 13.8, while the RecipeApiController includes the code from listing 13.9 where the code is refactored to use filters.

• DefaultTemplate - The default web app template for ASP.NET Core with Authentication, as discussed in section 14.3.
• RecipeApplication - The recipe application from chapter 13 with authentication added, as described in section 14.4. Also, the register page has been scaffolded to remove the references to external services, as described in section 14.5.
• RecipeApplicationWithNameClaim - The recipe application with an additional field added to the RegisterModel to record the FullName, as described in section 14.6. The field is added as an extra claim when the user registers, and is displayed in the menu bar when a user logs in.