Migrate nopCommerce to Arm on Microsoft Azure
Introduction
Set up an Arm-based environment
Create a nopCommerce endpoint benchmark baseline on Arm
Generate an SBOM and run .NET dependency discovery before migration
Choose a containerization path for the nopCommerce application
Tune the performance of the .NET application on Azure
Use the Arm MCP Server to optimize .NET performance
Next Steps
Migrate nopCommerce to Arm on Microsoft Azure
Introduction
Set up an Arm-based environment
Create a nopCommerce endpoint benchmark baseline on Arm
Generate an SBOM and run .NET dependency discovery before migration
Choose a containerization path for the nopCommerce application
Tune the performance of the .NET application on Azure
Use the Arm MCP Server to optimize .NET performance
Next Steps
Review frequently asked questions
These FAQs were 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.
Provision an Azure Cobalt-based environment as described in the
Azure Cobalt Learning Path
and keep the toolchain and runtime configuration stable across runs. The flow was validated with Ubuntu 24.04 LTS in
westus2 on an example size of Standard_D2ps_v6.Check out the specified release tag and run
git rev-parse --short=10 to capture the exact commit. Record the tag and short commit alongside the baseline results to avoid dependency drift.From the repository root, use
rg -n "<PackageReference|<ProjectReference" src to identify direct references and the owning projects. Then generate an SBOM and review transitive packages to uncover native payloads that could affect Arm deployment.Use the Dockerfile workflow as the default path for nopCommerce. Switch to .NET SDK publish when you want MSBuild-owned image metadata and have a repeatable plan for native packages, ensuring the SDK image matches Linux runtime dependencies and smoke-test results.
Stop the baseline process, set the runtime environment variables, and restart the application so the .NET runtime reads the new settings. Measure with fixed workloads and compare against the Arm endpoint baseline, keeping settings outside the code to switch profiles without rebuilding.