Who is this for?

This Learning Path is for .NET and platform engineers migrating a production .NET application to Arm-based infrastructure on Azure.

What will you learn?

After completing this Learning Path, you'll be able to perform the following tasks:

  • Build a pinned nopCommerce release and baseline on Arm with the same .NET toolchain
  • Produce an SBOM and resolve platform-specific dependency cascades
  • Containerize with Dockerfile and .NET SDK multi-arch publish workflows
  • Apply architecture-conditional runtime tuning with measured results
  • Use the Arm MCP Server to automate endpoint selection, test generation, and optimization planning

Prerequisites

Before starting, you'll need the following prerequisites:

  • Azure account with permissions to create virtual machines
  • An Azure Cobalt 100-based virtual machine
  • Azure CLI (az) installed locally
  • Docker and .NET 9 SDK familiarity
  • Basic Linux command-line knowledge

Summary

AI-assisted

This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
You’ll learn how to migrate a .NET nopCommerce application to an Arm-based virtual machine powered by Azure Cobalt 100, create a reproducible baseline, and apply measured runtime tuning. First, you’ll pin a specific nopCommerce release, verify a clean build, and capture an endpoint baseline on Arm to control for drift. By running dependency discovery and generating SBOM, you’ll surface direct, transitive, and native payloads. You’ll compare and choose a containerization path between a Dockerfile workflow and a .NET SDK publish with multi-architecture delivery guardrails. Finally, you’ll apply architecture-conditional runtime settings and validate them against fixed workloads.