Net core

1. Basic Features

a. Middleware

 Version: ASP.NET Core 1.0 (2016)

 Part of: ASP.NET Core
 Explanation: Middleware components are software components that
are assembled into an application pipeline to handle requests and
responses.
 Use Case: Adding functionality such as logging, authentication, or
error handling.
 Common Libraries: Built-in middleware options in ASP.NET Core.
 Code Snippet:
csharp
Copy code
public void Configure(IApplicationBuilder app, IWebHostEnvironment env) {
app.UseRouting();
app.UseAuthentication();
app.UseAuthorization();
app.UseEndpoints(endpoints => {
endpoints.MapControllers();
});
}

b. Dependency Injection (DI)

 Version: ASP.NET Core 1.0 (2016)

 Part of: ASP.NET Core
 Explanation: Built-in support for dependency injection, making it easy
to manage application dependencies.
 Use Case: Promotes loose coupling and enhances testability.
 Common Libraries: Microsoft.Extensions.DependencyInjection.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddTransient<IMyService, MyService>();
}

c. Razor Pages

 Version: ASP.NET Core 2.0 (2017)

 Part of: ASP.NET Core
 Explanation: Razor Pages is a page-based coding model that makes
building web UI easier and more productive.
 Use Case: Simplifying the development of web applications with a
more intuitive structure.
 Code Snippet:
csharp
Copy code
public class IndexModel : PageModel {
public void OnGet() {
// Logic for handling GET requests
}
}

d. API Development

 Version: ASP.NET Core 1.0 (2016)

 Part of: ASP.NET Core
 Explanation: ASP.NET Core provides features to build RESTful APIs
easily.
 Use Case: Creating services that can be consumed by frontend
applications or other services.
 Code Snippet:
csharp
Copy code
[ApiController]
[Route("api/[controller]")]
public class UsersController : ControllerBase {
[HttpGet]
public IEnumerable<User> GetAllUsers() {
// Logic to get all users
 }
}

2. Medium Features

a. Entity Framework Core (EF Core)

 Version: 1.0 (2016)

 Part of: Entity Framework
 Explanation: EF Core is an ORM framework that allows developers to
work with databases using .NET objects.
 Use Case: Simplifying data access and manipulation in applications.
 Common Libraries:
o Microsoft.EntityFrameworkCore.
 Code Snippet:
csharp
Copy code
public class ApplicationDbContext : DbContext {
public DbSet<User> Users { get; set; }
}

public class User {

public int Id { get; set; }
public string Name { get; set; }
}

b. Authentication and Authorization

 Version: ASP.NET Core 1.0 (2016)

 Part of: ASP.NET Core
 Explanation: Built-in support for authentication and authorization to
secure web applications.
 Use Case: Managing user access and roles in applications.
 Common Libraries:
o Microsoft.AspNetCore.Authentication.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddAuthentication("MyScheme")
.AddCookie("MyScheme", options => {
options.LoginPath = "/Account/Login";
});
}

c. Configuration Management

 Version: ASP.NET Core 1.0 (2016)

 Part of: ASP.NET Core
 Explanation: ASP.NET Core provides a flexible configuration system
that can read from various sources (JSON files, environment variables,
command-line arguments).
 Use Case: Managing application settings easily across different
environments.
 Common Libraries:
o Microsoft.Extensions.Configuration.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
var connectionString =
Configuration.GetConnectionString("DefaultConnection");
}

d. Logging

 Version: ASP.NET Core 1.0 (2016)

 Part of: ASP.NET Core
 Explanation: Built-in logging framework to log information and errors.
 Use Case: Monitoring application behavior and troubleshooting issues.
 Common Libraries:
o Microsoft.Extensions.Logging.
 Code Snippet:
csharp
Copy code
public class MyService {
private readonly ILogger<MyService> _logger;
 public MyService(ILogger<MyService> logger) {
_logger = logger;
}

public void DoWork() {

_logger.LogInformation("Doing work...");
}
}

3. Advanced Features of ASP.NET Core

a. Middleware

 Version: ASP.NET Core 1.0 (2016)

 Part of: ASP.NET Core
 Explanation: Middleware components are software components that
are assembled into an application pipeline to handle requests and
responses.
 Use Case: Adding functionality such as logging, authentication, or
error handling.
 Common Libraries: Built-in middleware options in ASP.NET Core.
 Code Snippet:
csharp
Copy code
public void Configure(IApplicationBuilder app, IWebHostEnvironment env) {
app.UseRouting();
app.UseAuthentication();
app.UseAuthorization();
app.UseEndpoints(endpoints => {
endpoints.MapControllers();
});
}
b. Dependency Injection (DI)

 Version: ASP.NET Core 1.0 (2016)

 Part of: ASP.NET Core
 Explanation: Built-in support for dependency injection, making it easy
to manage application dependencies.
 Use Case: Promotes loose coupling and enhances testability.
 Common Libraries: Microsoft.Extensions.DependencyInjection.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddTransient<IMyService, MyService>();
}

c. Entity Framework Core (EF Core)

 Version: 1.0 (2016)

 Part of: Entity Framework
 Explanation: EF Core is an ORM framework that allows developers to
work with databases using .NET objects.
 Use Case: Simplifying data access and manipulation in applications.
 Common Libraries:
o Microsoft.EntityFrameworkCore.
 Code Snippet:
csharp
Copy code
public class ApplicationDbContext : DbContext {
public DbSet<User> Users { get; set; }
}

public class User {

public int Id { get; set; }
public string Name { get; set; }
}

d. API Development

 Version: ASP.NET Core 1.0 (2016)

 Part of: ASP.NET Core
  Explanation: ASP.NET Core provides features to build RESTful APIs
easily.
 Use Case: Creating services that can be consumed by frontend
applications or other services.
 Common Libraries: Built-in support in ASP.NET Core.
 Code Snippet:
csharp
Copy code
[ApiController]
[Route("api/[controller]")]
public class UsersController : ControllerBase {
[HttpGet]
public IEnumerable<User> GetAllUsers() {
// Logic to get all users
}
}

e. Authentication and Authorization

 Version: ASP.NET Core 1.0 (2016)

 Part of: ASP.NET Core
 Explanation: Built-in support for authentication and authorization to
secure web applications.
 Use Case: Managing user access and roles in applications.
 Common Libraries: Microsoft.AspNetCore.Authentication.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddAuthentication("MyScheme")
.AddCookie("MyScheme", options => {
options.LoginPath = "/Account/Login";
});
}

f. Logging

 Version: ASP.NET Core 1.0 (2016)

 Part of: ASP.NET Core
  Explanation: Built-in logging framework to log information and errors.
 Use Case: Monitoring application behavior and troubleshooting issues.
 Common Libraries: Microsoft.Extensions.Logging.
 Code Snippet:
csharp
Copy code
public class MyService {
private readonly ILogger<MyService> _logger;

public MyService(ILogger<MyService> logger) {

_logger = logger;
}

public void DoWork() {

_logger.LogInformation("Doing work...");
}
}

g. Configuration Management

 Version: ASP.NET Core 1.0 (2016)

 Part of: ASP.NET Core
 Explanation: ASP.NET Core provides a flexible configuration system
that can read from various sources (JSON files, environment variables,
command-line arguments).
 Use Case: Managing application settings easily across different
environments.
 Common Libraries: Microsoft.Extensions.Configuration.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
var connectionString =
Configuration.GetConnectionString("DefaultConnection");
}

h. Health Checks

 Version: ASP.NET Core 2.2 (2018)

  Part of: ASP.NET Core
 Explanation: Health checks provide a way to monitor the health of
your application and its dependencies.
 Use Case: Ensuring that the application is running smoothly and is
responsive.
 Common Libraries: Microsoft.AspNetCore.Diagnostics.HealthChecks.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddHealthChecks();
}

public void Configure(IApplicationBuilder app) {

app.UseHealthChecks("/health");
}

i. API Documentation with Swagger

 Version: ASP.NET Core 2.0 (2017)

 Part of: ASP.NET Core
 Explanation: Swagger (OpenAPI) provides a way to document and
test APIs easily.
 Use Case: Automatically generating API documentation and testing
endpoints.
 Common Libraries: Swashbuckle.AspNetCore.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddSwaggerGen(c => {
c.SwaggerDoc("v1", new OpenApiInfo { Title = "My API", Version =
"v1" });
});
}

public void Configure(IApplicationBuilder app) {

app.UseSwagger();
app.UseSwaggerUI(c => {
 c.SwaggerEndpoint("/swagger/v1/swagger.json", "My API V1");
});
}

j. Data Protection

 Version: ASP.NET Core 2.0 (2017)

 Part of: ASP.NET Core
 Explanation: A system for protecting data, including user passwords
and sensitive data.
 Use Case: Ensuring that sensitive information is stored securely.
 Common Libraries: Microsoft.AspNetCore.DataProtection.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddDataProtection();
}

k. Caching

 Version: ASP.NET Core 1.0 (2016)

 Part of: ASP.NET Core
 Explanation: ASP.NET Core provides built-in support for caching data
to improve performance.
 Use Case: Storing frequently accessed data to reduce database load.
 Common Libraries: Microsoft.Extensions.Caching.Memory for in-
memory caching.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddMemoryCache();
}

public class MyService {

private readonly IMemoryCache _cache;

public MyService(IMemoryCache cache) {

 _cache = cache;
}

public string GetCachedData() {

return _cache.GetOrCreate("key", entry => {
entry.AbsoluteExpirationRelativeToNow = TimeSpan.FromMinutes(5);
return "Cached Value";
});
}
}

l. Cross-Origin Resource Sharing (CORS)

 Version: ASP.NET Core 1.0 (2016)

 Part of: ASP.NET Core
 Explanation: CORS is a mechanism that allows restricted resources on
a web page to be requested from another domain outside the domain
from which the resource originated.
 Use Case: Enabling cross-origin requests in web applications.
 Common Libraries: Microsoft.AspNetCore.Cors.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddCors(options => {
options.AddPolicy("AllowAll", builder => {
builder.AllowAnyOrigin()
.AllowAnyMethod()
.AllowAnyHeader();
});
});
}

public void Configure(IApplicationBuilder app) {

app.UseCors("AllowAll");
}
m. Razor Pages

 Version: ASP.NET Core 2.0 (2017)

 Part of: ASP.NET Core
 Explanation: Razor Pages is a page-based coding model that makes
building web UI easier and more productive.
 Use Case: Simplifying the development of web applications.
 Code Snippet:
csharp
Copy code
public class IndexModel : PageModel {
public void OnGet() {
// Logic for handling GET requests
}
}

n. SignalR

 Version: 2.1 (2016), integrated with ASP.NET Core

 Part of: ASP.NET Core
 Explanation: SignalR is a library for adding real-time web functionality
to applications. It allows server-side code to push content to connected
clients instantly.
 Use Case: Building chat applications, live notifications, or real-time
dashboards.
 Common Libraries: Microsoft.AspNetCore.SignalR.
 Code Snippet:
csharp
Copy code
public class ChatHub : Hub {
public async Task SendMessage(string user, string message) {
await Clients.All.SendAsync("ReceiveMessage", user, message);
}
}

o. Globalization and Localization

 Version: ASP.NET Core 1.0 (2016)

 Part of: ASP.NET Core
  Explanation: Allows applications to support multiple languages and
cultures.
 Use Case: Providing localized content based on user preferences.
 Common Libraries: Microsoft.Extensions.Localization.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddLocalization(options => options.ResourcesPath =
"Resources");
}

public void Configure(IApplicationBuilder app) {

var supportedCultures = new[] { "en-US", "fr-FR" };
var localizationOptions = new RequestLocalizationOptions {
DefaultRequestCulture = new RequestCulture("en-US"),
SupportedCultures = supportedCultures.Select(c => new
CultureInfo(c)).ToList(),
SupportedUICultures = supportedCultures.Select(c => new
CultureInfo(c)).ToList()
};
app.UseRequestLocalization(localizationOptions);
}

4. Extra (Cutting Edge) Features of ASP.NET Core

a. ASP.NET Core Identity

 Version: ASP.NET Core 2.0 (2017)

 Part of: ASP.NET Core
 Explanation: ASP.NET Core Identity is a membership system that
adds login functionality to your application.
 Use Case: Managing user accounts, including registration, login,
password recovery, and role management.
 Common Libraries:
o Microsoft.AspNetCore.Identity.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddDbContext<ApplicationDbContext>(options =>

options.UseSqlServer(Configuration.GetConnectionString("DefaultConnection
")));

services.AddIdentity<IdentityUser, IdentityRole>()
.AddEntityFrameworkStores<ApplicationDbContext>()
.AddDefaultTokenProviders();
}

b. OpenAPI and Swagger

 Version: ASP.NET Core 2.0 (2017)

 Part of: ASP.NET Core
 Explanation: OpenAPI (formerly Swagger) is a specification for
documenting RESTful APIs, and ASP.NET Core integrates well with it via
libraries like Swashbuckle.
 Use Case: Automatically generating documentation for APIs and
providing a UI for testing endpoints.
 Common Libraries:
o Swashbuckle.AspNetCore.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddSwaggerGen(c => {
c.SwaggerDoc("v1", new OpenApiInfo { Title = "My API", Version =
"v1" });
});
}

public void Configure(IApplicationBuilder app) {

app.UseSwagger();
app.UseSwaggerUI(c => {
c.SwaggerEndpoint("/swagger/v1/swagger.json", "My API V1");
 });
}

c. gRPC

 Version: ASP.NET Core 3.0 (2019)

 Part of: ASP.NET Core
 Explanation: gRPC is a high-performance, open-source RPC (Remote
Procedure Call) framework that can run in any environment.
 Use Case: Building efficient microservices and real-time
communication systems.
 Common Libraries:
o Grpc.AspNetCore.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddGrpc();
}

public void Configure(IApplicationBuilder app) {

app.UseEndpoints(endpoints => {
endpoints.MapGrpcService<GreeterService>();
});
}

d. Health Checks

 Version: ASP.NET Core 2.2 (2018)

 Part of: ASP.NET Core
 Explanation: Health checks provide a way to monitor the health of
your application and its dependencies.
 Use Case: Ensuring that the application is running smoothly and is
responsive.
 Common Libraries:
o Microsoft.AspNetCore.Diagnostics.HealthChecks.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddHealthChecks();
}

public void Configure(IApplicationBuilder app) {

app.UseHealthChecks("/health");
}

e. SignalR

 Version: ASP.NET Core 2.1 (2016)

 Part of: ASP.NET Core
 Explanation: SignalR is a library for adding real-time web functionality
to applications, allowing server-side code to push content to connected
clients instantly.
 Use Case: Building chat applications, live notifications, or real-time
dashboards.
 Common Libraries:
o Microsoft.AspNetCore.SignalR.
 Code Snippet:
csharp
Copy code
public class ChatHub : Hub {
public async Task SendMessage(string user, string message) {
await Clients.All.SendAsync("ReceiveMessage", user, message);
}
}

f. Docker Support

 Version: ASP.NET Core 2.1 (2017)

 Part of: ASP.NET Core
 Explanation: ASP.NET Core applications can easily be containerized
and deployed using Docker.
 Use Case: Simplifying deployment and scaling in cloud environments.
 Common Libraries:
o Dockerfile template support in Visual Studio.
 Code Snippet (Dockerfile):
dockerfile
Copy code
FROM mcr.microsoft.com/dotnet/aspnet:5.0 AS base
WORKDIR /app
COPY . .
ENTRYPOINT ["dotnet", "MyApp.dll"]

g. Globalization and Localization

 Version: ASP.NET Core 1.0 (2016)

 Part of: ASP.NET Core
 Explanation: Globalization and localization support allows applications
to adapt to different cultures and languages.
 Use Case: Providing localized content based on user preferences.
 Common Libraries:
o Microsoft.Extensions.Localization.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddLocalization(options => options.ResourcesPath =
"Resources");
}

public void Configure(IApplicationBuilder app) {

var supportedCultures = new[] { "en-US", "fr-FR" };
var localizationOptions = new RequestLocalizationOptions {
DefaultRequestCulture = new RequestCulture("en-US"),
SupportedCultures = supportedCultures.Select(c => new
CultureInfo(c)).ToList(),
SupportedUICultures = supportedCultures.Select(c => new
CultureInfo(c)).ToList()
};
app.UseRequestLocalization(localizationOptions);
}

h. API Documentation with Swagger

 Version: ASP.NET Core 2.0 (2017)

 Part of: ASP.NET Core
  Explanation: Swagger (OpenAPI) provides a way to document and
test APIs easily.
 Use Case: Automatically generating API documentation and testing
endpoints.
 Common Libraries:
o Swashbuckle.AspNetCore.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddSwaggerGen(c => {
c.SwaggerDoc("v1", new OpenApiInfo { Title = "My API", Version =
"v1" });
});
}

public void Configure(IApplicationBuilder app) {

app.UseSwagger();
app.UseSwaggerUI(c => {
c.SwaggerEndpoint("/swagger/v1/swagger.json", "My API V1");
});
}

i. Caching

 Version: ASP.NET Core 1.0 (2016)

 Part of: ASP.NET Core
 Explanation: ASP.NET Core provides built-in support for caching to
improve application performance.
 Use Case: Storing frequently accessed data to reduce database load.
 Common Libraries:
o Microsoft.Extensions.Caching.Memory for in-memory caching.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddMemoryCache();
}
public class MyService {
private readonly IMemoryCache _cache;

public MyService(IMemoryCache cache) {

_cache = cache;
}

public string GetCachedData() {

return _cache.GetOrCreate("key", entry => {
entry.AbsoluteExpirationRelativeToNow = TimeSpan.FromMinutes(5);
return "Cached Value";
});
}
}

j. Health Checks

 Version: ASP.NET Core 2.2 (2018)

 Part of: ASP.NET Core
 Explanation: Health checks provide a way to monitor the health of
your application and its dependencies.
 Use Case: Ensuring that the application is running smoothly and is
responsive.
 Common Libraries:
o Microsoft.AspNetCore.Diagnostics.HealthChecks.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddHealthChecks();
}

public void Configure(IApplicationBuilder app) {

app.UseHealthChecks("/health");
}

k. gRPC

 Version: ASP.NET Core 3.0 (2019)

  Part of: ASP.NET Core
 Explanation: gRPC is a high-performance, open-source RPC (Remote
Procedure Call) framework that can run in any environment.
 Use Case: Building efficient microservices and real-time
communication systems.
 Common Libraries:
o Grpc.AspNetCore.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddGrpc();
}

public void Configure(IApplicationBuilder app) {

app.UseEndpoints(endpoints => {
endpoints.MapGrpcService<GreeterService>();
});
}

l. OpenAPI and Swagger Integration

 Version: ASP.NET Core 2.0 (2017)

 Part of: ASP.NET Core
 Explanation: OpenAPI (formerly Swagger) allows for automated API
documentation and testing.
 Use Case: Helps in generating interactive API documentation.
 Common Libraries:
o Swashbuckle.AspNetCore.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddSwaggerGen(c => {
c.SwaggerDoc("v1", new OpenApiInfo { Title = "My API", Version =
"v1" });
});
}
public void Configure(IApplicationBuilder app) {
app.UseSwagger();
app.UseSwaggerUI(c => {
c.SwaggerEndpoint("/swagger/v1/swagger.json", "My API V1");
});
}

m. API Versioning

 Version: ASP.NET Core 2.1 (2018)

 Part of: ASP.NET Core
 Explanation: API versioning allows you to manage changes to your
API without breaking existing clients.
 Use Case: Ensuring backward compatibility while evolving the API.
 Common Libraries:
o Microsoft.AspNetCore.Mvc.Versioning.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddApiVersioning(options => {
options.AssumeDefaultVersionWhenUnspecified = true;
options.DefaultApiVersion = new ApiVersion(1, 0);
});
}

n. CORS (Cross-Origin Resource Sharing)

 Version: ASP.NET Core 1.0 (2016)

 Part of: ASP.NET Core
 Explanation: CORS is a security feature that allows or restricts
resources on a web page to be requested from another domain outside
the domain from which the resource originated.
 Use Case: Enabling or restricting cross-origin requests in web
applications.
 Common Libraries:
o Microsoft.AspNetCore.Cors.
 Code Snippet:
csharp
Copy code
public void ConfigureServices(IServiceCollection services) {
services.AddCors(options => {
options.AddPolicy("AllowAll", builder => {
builder.AllowAnyOrigin()
.AllowAnyMethod()
.AllowAnyHeader();
});
});
}

public void Configure(IApplicationBuilder app) {

app.UseCors("AllowAll");
}