ASP.NET Core Documentation

This sample demonstrates different ways to activate middleware in ASP.NET Core, specifically focusing on scenarios described in 'Factory-based middleware activation'. It compares conventional middleware activation against activation via the IMiddleware interface.

The sample implements middleware that:

1. Reads a value from a query string parameter named key.
2. Uses an injected database context (a scoped service) to record that value in an in-memory database.

This demonstrates how middleware can interact with scoped services through different activation patterns.

HTTP.sys is a Windows-only web server for ASP.NET Core that serves as an alternative to Kestrel. It is a mature, full-featured web server that provides robustness and security, often used when exposing a server directly to the internet without IIS or when specific features not available in Kestrel are required.

Key Features:

• Windows Authentication
• Port sharing
• HTTPS with SNI
• HTTP/2 over TLS (Windows 10 or later)
• Direct file transmission
• Response caching
• WebSockets (Windows 8 or later)

Important Compatibility Notes:

• Not compatible with the ASP.NET Core Module.
• Cannot be used with IIS or IIS Express.
• Supported Windows Versions: Windows 7 or later; Windows Server 2008 R2 or later.

NSwag provides several ways to generate API client code (such as C# or TypeScript) from a Swagger/OpenAPI specification:

• NSwagStudio: A Windows desktop application for visual code generation.
• NuGet Packages: Use NSwag.CodeGeneration.CSharp or NSwag.CodeGeneration.TypeScript to perform generation directly within your project.
• Command Line: Use the NSwag CLI tool.
• MSBuild: Use the NSwag.MSBuild NuGet package to integrate generation into your build process.
• Unchase OpenAPI (Swagger) Connected Service: A Visual Studio extension that generates C# or TypeScript clients and can also generate C# controllers for OpenAPI services.

This sample demonstrates how to use the ASP.NET Core URL rewriting middleware to implement URL redirects and URL rewriting rules.

When a rule is applied:

• Redirects: The client receives a redirect response (e.g., 301 or 302) and is instructed to request a different URL.
• Rewrites: The request URL is changed internally. The client continues to request the original URL, but the middleware processes the request using the rewritten path. For static files, the Static file middleware serves the file based on the rewritten path.

The DbContext is the main class that coordinates Entity Framework functionality for a given data model. It derives from Microsoft.EntityFrameworkCore.DbContext.

Inside the DbContext, you define DbSet<TEntity> properties.

• An entity set (represented by a DbSet) typically corresponds to a database table.
• An entity corresponds to a single row in that table.

Example: Changing a DbSet<Student> to DbSet<Students> updates the entity set name to be plural, which is a common convention.

A standard Razor Pages project contains the following key components:

• Pages folder: Contains Razor pages. Each page consists of a .cshtml file (HTML with Razor syntax) and a .cshtml.cs file (C# code-behind for handling page events). Supporting files like _Layout.cshtml (common UI elements) begin with an underscore.
• wwwroot folder: Stores static assets such as HTML, JavaScript, and CSS files.
• appsettings.json: Stores configuration data, such as database connection strings.
• Program.cs: The entry point that configures the WebApplicationBuilder, adds Razor Pages to the Dependency Injection (DI) container, and defines the middleware pipeline.