dotnet-ado-publish

Publish .NET NuGet packages and container images from Azure DevOps pipelines.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/rudironsoni/dotnet-agent-harness --skill dotnet-ado-publish-rudironsoni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-ado-publish
Source: https://github.com/rudironsoni/dotnet-agent-harness/tree/main/.rulesync/skills/dotnet-ado-publish
Command: npx skills add https://github.com/rudironsoni/dotnet-agent-harness --skill dotnet-ado-publish-rudironsoni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of publishing .NET artifacts, including NuGet packages and container images, within Azure DevOps pipelines.

Core Features & Use Cases

  • NuGet Publishing: Push packages to Azure Artifacts or nuget.org.
  • Container Publishing: Build and push Docker images to Azure Container Registry (ACR).
  • Artifact Staging: Upload build outputs as pipeline artifacts for downstream consumption.
  • Use Case: Automatically publish your .NET library as a NuGet package to Azure Artifacts whenever a new Git tag is pushed, ensuring your team has access to the latest version.

Quick Start

Use the dotnet-ado-publish skill to push NuGet packages to Azure Artifacts.

Frequently Asked Questions about dotnet-ado-publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish NuGet packages to Azure Artifacts from an Azure DevOps pipeline?

You can publish NuGet packages to Azure Artifacts from an Azure DevOps pipeline by configuring a CI/CD task to pack and push the .NET project outputs directly to your organization's feed.

Can I push .NET container images to Azure Container Registry using Azure DevOps?

Yes, .NET container images can be built and pushed to Azure Container Registry (ACR) by integrating Docker build and push tasks directly within your Azure DevOps pipelines.

What is the best way to stage .NET build outputs for multi-stage release pipelines?

Staging .NET build outputs for multi-stage releases is achieved using PublishPipelineArtifact@1 and PublishBuildArtifacts@1, which upload build outputs for downstream pipeline consumption.

Does this approach support publishing .NET artifacts to nuget.org as well as Azure Artifacts?

Yes, the publishing workflow supports pushing NuGet packages to both Azure Artifacts for internal team distribution and nuget.org for public consumption directly from Azure DevOps.

How do I automatically publish a .NET library as a NuGet package when a Git tag is pushed?

Automatically publishing a .NET library upon a Git tag push involves configuring an Azure DevOps pipeline trigger that packs the code and pushes the resulting NuGet package.

When do I need to use PublishBuildArtifacts@1 versus PublishPipelineArtifact@1 in .NET pipelines?

You need PublishPipelineArtifact@1 for modern multi-stage release pipelines, while PublishBuildArtifacts@1 is used for staging .NET build outputs in classic release pipeline workflows.