Deploy Node/React/Next.js application to Azure App Service

 To deploy your Next.js dashboard (with App Router) to Azure App Service, follow these steps. 

Azure supports Next.js out-of-the-box with static and server-rendered content, including middleware.

microsoft/copilot-metrics-dashboard

>>C:\copilot-metrics-dashboard\src\dashboard>

1. Prepare Your App for Azure, Ensure your app is ready:

package.json must have a build and start script:

{

  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start"
  }
}

You're using App Router (e.g., app/page.tsx), so next build will generate both static and server-rendered routes.

2. Create Production Build (Locally or via CI), run through VSC

npm install

npm run build

npm start - This confirms your app runs as a production server with next start.

Make sure the build completes successfully.

Install Docker CLI on Windows

 

Step-by-Step: Install Docker CLI on Windows

1. Download the Docker CLI Binary

• Visit the official Docker static binaries repository:

  https://download.docker.com/win/static/stable/x86_64/

• Download the latest .zip archive, for example: docker-28.3.0.zip

2. Extract the Archive

• Extract the contents of the .zip file to a directory of your choice, such as: C:\Tools\DockerCLI

• Inside this directory, you should find the docker.exe file.

3. Add Docker CLI to System PATH

• Open PowerShell as Administrator and run the following command to add the directory to your system's PATH:

  [System.Environment]::SetEnvironmentVariable("Path", $env:Path + ";C:\Tools\DockerCLI", [System.EnvironmentVariableTarget]::Machine)
  

  Replace C:\Tools\DockerCLI with the path where you extracted docker.exe.

• Restart your terminal to apply the changes.

4. Verify the Installation

• Open a new PowerShell or Command Prompt and run: docker version

  You should see output similar to:

  Client: Docker CLI

MicroSoft Blazor

 Blazor

Today's web development, use both server-side (C#, Java,...) and client-side (JavaScript frameworks like Angular, React,..) technologies. 

Use C# both for server & client side development, that's Blazor. Blazor lets you build interactive web UIs using C# instead of JavaScript.

Blazor can run client-side C# code (or any type of code) directly in the browser, using WebAssembly. It runs in the same security sandbox as JavaScript frameworks like Angular, React, etc. 

WebAssembly is based on open web standards without using plug-ins or code transpilation. It works in all modern browsers including mobile browsers.  

There are 2 Blazor hosting models: Blazor WebAssembly (the client-side) and Blazor Server (the server) .

SQL Server Stretch Database

Stretch Database

Data can be split between on-premises and cloud storage. 

With Stretch Database, cold/audit data is kept in the cloud and data remains available for users to

query, might be a small amount of additional latency associated with queries. Data in the cloud is backed up automatically. 

With Stretch Database, active data is kept on-premises for maximum performance and reduce storage requirements both for data and backups (it run quicker than standard backups). 

It requires no changes to new or existing TSQL queries. 

Azure SQL

Search Azure SQL
3 Options to Choose

Large Volume Data Migration to Azure using Azure Data Box

Migrating Large volume of data(like Terabytes or Petabytes) from on-premises to Azure using Azure Data Box.

Two types of data transfer options: Offline & Online

Offline - choose

1. More than 5 TB, no good bandwidth connectivity

2. Data can be upload to any one of storage: Block Blob, Page Blob, Managed Disk, File Storage

3. Four Data Box options available to choose 

Deploy ASP.NET CORE WEB API to Containers and Azure Kubernetes using Concourse pipeline

GitHub Source Code
https://github.com/mkader/ConcourseAzureBlobContainerK8s

1. Create and Pull ASP.NET Core WEB API source code from GitHub using Concourse resource. 2. Running unit test using Concourse job. 3. Generate a Docker Container image. 4. Publishing it into a Azure Container Registry. 5. Generate a tar(zip) file 6. Store it into a Azure Blob Storage. 7. Generate semantic version and tag it into Docker Container image. 8. Deploys a Docker Container image from Azure Container Registry to Azure Kubernetes. 9. Add Coverlet Code coverage and SonarQube Code Analysis.