Bagaimana untuk menyediakan saluran paip CI/CD untuk projek C# pada Tindakan GitHub?

使用GitHub Actions可在10分钟内搭建C#项目的CI/CD流水线，关键在于匹配setup-dotnet版本与项目TargetFramework，按restore、build、test、pack顺序执行，并仅在带v前缀的标签提交时部署。

You can set up a working CI/CD pipeline for a C# project on GitHub Actions in under 10 minutes — no third-party services or custom runners needed. The key is using the right actions/setup-dotnet version and matching it to your project’s TargetFramework.

Use actions/setup-dotnet with correct SDK version

GitHub Actions doesn’t auto-detect which .NET SDK your project needs. If you use a mismatched version (e.g., 7.0.x for a net6.0 project), dotnet build fails with “The SDK ‘Microsoft.NET.Sdk’ specified could not be found”.

• Check your .csproj: look for <TargetFramework>net6.0</TargetFramework> or <TargetFrameworks>net6.0;net8.0</TargetFrameworks>
• In your workflow, pin the SDK explicitly: with: { dotnet-version: '6.0.x' } — avoid '6.x' unless you’re certain
• Prefer 6.0.402 over 6.0.400 if targeting .NET 6.0.4xx patch releases — some minor patches fix restore bugs on Ubuntu runners

Restore, build, test, and pack in order — don’t skip dotnet test

dotnet test runs silently by default and exits 0 even when tests are skipped or fail silently due to missing Microsoft.NET.Test.Sdk. You’ll think CI passed when it didn’t.

• Always include --no-restore after the initial dotnet restore to avoid redundant network calls
• Add --configuration Release to dotnet build and dotnet test — Debug builds may hide linker or AOT issues
• For xUnit/NUnit, verify your test project has <PackageReference Include="Microsoft.NET.Test.Sdk" Version="17.8.0" /> — older versions break on .NET 7+

name: .NET CI
on: [push, pull_request]
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Setup .NET
        uses: actions/setup-dotnet@v4
        with:
          dotnet-version: '6.0.402'
      - name: Restore dependencies
        run: dotnet restore ./MyApp.sln
      - name: Build
        run: dotnet build ./MyApp.sln --configuration Release --no-restore
      - name: Test
        run: dotnet test ./MyApp.Tests.csproj --configuration Release --no-restore --verbosity normal
      - name: Pack
        run: dotnet pack ./MyApp.csproj --configuration Release --no-restore --output ./artifacts

Deploy only on tagged commits — avoid accidental releases

Using on: push alone will trigger deployment on every commit, including feature branches. That breaks semantic versioning and floods your NuGet feed.

• Use on: push: tags: ['v*'] to limit deployment to annotated tags like v1.2.0
• Add if: startsWith(github.ref, 'refs/tags/v') as a guard in deploy steps — prevents misfires from lightweight tags
• For NuGet push, store your API key as a GitHub secret named NUGET_API_KEY, not in plain text

The biggest pitfall isn’t syntax — it’s assuming dotnet build implies correctness. A passing build hides broken references, missing analyzers, or test assembly mismatches. Always run dotnet test with --verbosity normal and check that output includes “Passed: X” — not just “Test Run Successful”.

Atas ialah kandungan terperinci Bagaimana untuk menyediakan saluran paip CI/CD untuk projek C# pada Tindakan GitHub?. Untuk maklumat lanjut, sila ikut artikel berkaitan lain di laman web China PHP!