Quantcast
Channel: Active questions tagged nuget-package - Stack Overflow
Viewing all articles
Browse latest Browse all 3067

DevOps Pipeline NuGet publish misses my resource DLL. Do I need a NUSPEC file?

$
0
0

I have a tiny .NET 5.0 C# project ("MyComponent") that builds in Azure DevOps YAML pipelines and publishes a NuGet package to an internal feed. It has English strings and French strings so it generates two outputs: MyComponent.dll and MyComponent.resources.dll

\net5.0-windows    |    |-- MyComponent.dll    |    \fr        |        |-- MyComponent.resources.dll

It builds and publishes the component to my internal feed. And my other projects succeed in pulling it.Unfortunately when they pull it, the resources dll does NOT get pulled to the client's build tree. Only MyComponent.dll is pulled. So I guess it's not getting published properly.

This is the entire publish task

[Edited to show the correct task. When I first wrote this question I inadvertently put the publishing of the symbols, not the project itself]

- task: NuGetCommand@2  displayName: 'Pack NuGet Package'  inputs:    command: 'pack'    verbosityPack: Detailed    packagesToPack: '**/MyComponent.csproj'    configuration: 'x64\Release'    versioningScheme: byBuildNumber    includeSymbols: true

How do I make this thing also publish the resources dll in the "fr" subdirectory?

Is there some syntax option on this command task that I am missing? The docs list so many options, I'm lost. Do I need to write a .NUSPEC file?

-Joe


Viewing all articles
Browse latest Browse all 3067

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>