ci: migrate Azure Pipeline from Windows/MSBuild to Linux/.NET CLI

[nanotaboada]

• Replace windows-latest with ubuntu-latest for faster builds
• Remove legacy VSBuild/VSTest tasks in favor of DotNetCoreCLI@2
• Add NuGet package caching based on packages.lock.json hash
• Add explicit checkout step for clarity
• Add trigger for feature/* branches and pull requests
• Remove code coverage publishing (handled by GitHub Actions)
• Add descriptive comments mapping Azure Pipelines to GitHub Actions syntax
• Align step names with GitHub Actions workflow for consistency

Summary by CodeRabbit

• Documentation

  • Updated architecture diagram (orientation and connections) and revised legal text to a production-appropriate disclaimer.

• Chores

  • Migrated CI to modern Linux/.NET 8 pipeline: updated platform, triggers, SDK/tooling, and streamlined restore/build/test workflow with preserved test publishing.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Switched CI from a Windows/.NET Framework MSBuild flow to a dotnet CLI-based pipeline targeting ASP.NET Core 8.0 on Linux; updated pipeline triggers and agent, plus README diagram orientation, an added diagram edge, and revised legal text.

Changes

Cohort / File(s)	Summary
Documentation README.md	Changed Mermaid diagram orientation from left-to-right to top-to-bottom, added an edge from Models to Mappings, and updated the Legal section text to remove "proof-of-concept" phrasing and adjust ownership/disclaimer language.
CI/CD Pipeline azure-pipelines.yml	Replaced legacy Windows/MSBuild pipeline with a Linux-based ASP.NET Core 8.0 flow: updated triggers (including master and feature/*), switched agent pool to ubuntu-latest, set dotnet-related env vars (DOTNET_SKIP_FIRST_TIME_EXPERIENCE, DOTNET_NOLOGO), added UseDotNet task, and converted NuGet/VSBuild/VSTest steps into explicit dotnet CLI tasks (restore, build, test) with test result publishing.

Sequence Diagram(s)

mermaid
sequenceDiagram
autonumber
participant Dev as Developer (push/PR)
participant AZP as Azure Pipeline
participant Agent as Build Agent (ubuntu-latest)
participant SDK as UseDotNet (install SDK)
participant NuGet as NuGet Restore
participant Dotnet as dotnet build/test
participant Reporter as Test Results Publisher

Dev->>AZP: push / PR triggers pipeline
AZP->>Agent: provision agent
Agent->>SDK: install .NET 8.0 SDK
Agent->>NuGet: restore packages
Agent->>Dotnet: dotnet build --configuration $(BuildConfiguration)
Agent->>Dotnet: dotnet test --logger "trx"
Dotnet->>Reporter: emit test results
Reporter->>AZP: publish test results

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Review azure-pipelines.yml for correct SDK versioning, cache and restore behavior, test result publishing paths, and any condition/trigger semantics.
• Verify migration removed any Windows/MSBuild-specific settings that might be required elsewhere (e.g., signing, NuGet feeds, or tooling).
• Confirm README diagram change matches architecture and legal wording meets project/legal requirements.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely summarizes the main change: migrating Azure Pipeline configuration from Windows/MSBuild to Linux/.NET CLI. It matches the primary focus of the changeset and uses specific, clear terminology.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/azure-pipeline-linux-dotnet-cli

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f0612fa and 557b2ad.

📒 Files selected for processing (2)

• README.md (3 hunks)
• azure-pipelines.yml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Codacy Static Code Analysis

🔇 Additional comments (6)

azure-pipelines.yml (6)

5-11: Pipeline triggers correctly configured for feature branches and PRs.

The trigger configuration aligns with the migration objective and clearly documents the GitHub Actions equivalent in comments.

---

13-22: Agent pool and environment variables are well-configured.

The switch to ubuntu-latest and the environment variable choices (especially DOTNET_SKIP_FIRST_TIME_EXPERIENCE and DOTNET_NOLOGO) follow CI best practices.

---

26-29: Explicit checkout step improves readability.

Good practice to make the implicit explicit, and the comment clearly documents the reasoning.

---

31-39: NuGet caching strategy is solid.

The cache key using packages.lock.json provides good reproducibility. Verify that the repo maintains this lock file for optimal caching efficiency.

---

41-47: SDK setup correctly targets .NET 8.

The UseDotNet@2 configuration with performMultiLevelLookup provides appropriate flexibility for the CI environment.

---

67-76: Test discovery pattern correctly matches the repository's test projects.

The pattern **/*Tests/*.csproj successfully discovers the test project in this repository: ./test/Dotnet.Samples.AspNetCore.WebApi.Tests/Dotnet.Samples.AspNetCore.WebApi.Tests.csproj. The repository follows a standard naming convention with test projects in a dedicated test/ folder and project names suffixed with .Tests. No test projects are being skipped by this pattern.

Likely an incorrect or invalid review comment.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.00%	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (6daa47f)	1152	196	17.01%
Head commit (557b2ad)	1152 (+0)	196 (+0)	17.01% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#316)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud