Software Development Blog

Blazor comes in three hosting models: Blazor Server , Blazor WebAssembly (WASM) , and Blazor Hybrid . Each model has unique requirements for setup in the Program.cs file and routing. Let's break down what is needed for each. 1. Blazor Server Blazor Server runs the app on the server, with the UI updates sent to the client over a real-time SignalR connection. Key Setup in Program.cs csharp var builder = WebApplication.CreateBuilder(args); // Add Blazor Server services builder.Services.AddServerSideBlazor() .AddCircuitOptions(options => options.DetailedErrors = true ); // Optional: Enable detailed errors var app = builder.Build(); // Map the Blazor Server app app.MapBlazorHub(); // Maps SignalR hub for real-time communication app.MapFallbackToPage( "/_Host" ); // Fallback route to load the app app.Run(); Router The _Host.cshtml file serves as the entry point. Routes are managed server-side. Example: razor <Router AppAssembly="typeof(Program).Ass...

A multi-stage build in Docker allows you to use multiple FROM statements in a single Dockerfile to create separate stages for building and running an application. For example, in the first stage, you can use a large image with the SDK (e.g., mcr.microsoft.com/dotnet/sdk ) to compile and publish the application. In the second stage, you copy the build output to a lightweight runtime-only image (e.g., mcr.microsoft.com/dotnet/aspnet ) to create the final container. This approach significantly reduces the size of the final image because only the application and its dependencies are included, while the build tools and intermediate files are discarded. This results in smaller, more secure, and more efficient images. Each image used in a multi-stage Docker build can have a specific tag that identifies the exact version or variant of the image. For example, in the build stage, you might use a tagged SDK image like mcr.microsoft.com/dotnet/sdk:9.0 to ensure the application is compiled with...

  When you select "Add Docker Support" in Visual Studio, it integrates Docker into your .NET project to enable containerization. This involves making several changes to your project and its configuration files to facilitate running and debugging the application in a Docker container. Here’s what "Add Docker Support" does in detail: 1. Adds a Dockerfile Visual Studio generates a Dockerfile tailored to your project's type (e.g., Web API, Console App). This file contains the instructions for building and running your application in a Docker container. Example Dockerfile for a Web API: dockerfile FROM mcr.microsoft.com/dotnet/aspnet:9.0 AS base WORKDIR /app EXPOSE 80 EXPOSE 443 FROM mcr.microsoft.com/dotnet/sdk:9.0 AS build WORKDIR /src COPY ["MyWebAPI/MyWebAPI.csproj", "./"] RUN dotnet restore "MyWebAPI.csproj" COPY . . WORKDIR "/src/MyWebAPI" RUN dotnet build "MyWebAPI.csproj" -c Release -o /app/build FROM bui...

Docker provides a consistent runtime environment for running .NET applications, enabling seamless development and deployment across various platforms. This guide explains how to configure any .NET program to run in Docker, explores project types compatible with Docker, and provides examples for Web API and Console Applications . Understanding the Docker Configuration in launchSettings.json The launchSettings.json file in .NET projects includes profiles for debugging and running applications. When configured for Docker, a typical profile might look like this: json "Container (Dockerfile)" : { "commandName" : "Docker" , "launchUrl" : "{Scheme}://{ServiceHost}:{ServicePort}" , "environmentVariables" : { "ASPNETCORE_HTTPS_PORTS" : "8081" , "ASPNETCORE_HTTP_PORTS" : "8080" } , "publishAllPorts" : true , "useSSL" : true } Key Propertie...

Dockerfiles are essential for containerizing applications, allowing developers to package code, dependencies, and runtime environments into lightweight, portable containers. In this article, we’ll explore a multi-stage Dockerfile designed for a .NET Web API project named SampleWebAPI . This Dockerfile employs best practices to create a lightweight and secure container image while maintaining an efficient build process. Dockerfile Overview This Dockerfile is structured into multiple stages, each focusing on a specific phase of the containerization process: Debug Stage : Prepares the runtime environment for debugging. Build Stage : Compiles the application code. Publish Stage : Prepares the application for deployment. Runtime Stage : Creates the final container image for production. Debug Stage dockerfile FROM mcr.microsoft.com/dotnet/aspnet:9.0 AS base USER $APP_UID WORKDIR /app EXPOSE 8080 EXPOSE 8081 Base Image : Uses the official ASP.NET Core runtime image ( aspnet:9.0 ) to provide...

Here’s a breakdown of the functionality in this class ( Program.cs ), which configures an ASP.NET Core Web API application with authentication, user management, and authorization features. The code is centered around Google OAuth and role-based user management. 1. Services Configuration Minimal asp.net core API Scans and discovers all Minimal API endpoints (routes added via methods like MapGet, MapPost, etc.). csharp builder.Services.AddEndpointsApiExplorer(); Swagger Setup What it does : Adds Swagger support for API documentation. Includes a Bearer token security scheme to secure the API endpoints that require authentication. csharp builder.Services.AddSwaggerGen(c => { c.SwaggerDoc( "v1" , new OpenApiInfo { Title = "Minimal Web API" ,           Version = "v1" }); c.AddSecurityDefinition( "Bearer" , ...); c.AddSecurityRequirement( new OpenApiSecurityRequirement() { ... }); }); Authentication Configuration Default Scheme : Se...