Skip to content

Publishing a package from a nuspec is broken #4341

Closed
@RikkiGibson

Description

@RikkiGibson

Quoting @jmarolf:

Arcade broke generating a nuget package from a nuspec in #2003. We will need to submit a PR to arcade to do the correct thing in the presence of nuspec files. The root of the issue is that is appends the CommonMetadataElements xml in to the NuspecProperties list. The pack command does not know how to extract key-value pairs from xml

Original comment: dotnet/roslyn-tools#574 (comment)
Related to: dotnet/roslyn-tools#577

I am interested in fixing this if I can, but I could use some pointers on stuff like how to use a local Microsoft.DotNet.Arcade.Sdk and how to do a dry run of a NuGet pack.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions