Skip to content

[BUG] - Versioning doesn't support NuGet project reference dependencies #79

@smaillet

Description

@smaillet

.NET Framework Used:

  • .NET 9.0
  • Something else

OS Environment:

  • Windows 10
  • Windows 10 IoT Core
  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016

I have already...

  • Reproduced the problem using the latest stable release.
  • Reviewed the documentation.
  • Reviewed the current issues to check that the issue isn't already known.

Description:
Nuspec file generated by pack command for a project with project references will have an incorrect version of 1.0.0

Steps to reproduce the problem:

  • Reviewed the documentation.
  • Included Sample code or link to repository/gist to reproduce the bug (This is the fastest way to a resolution as it reduces the time to reproduce the problem. The smaller the sample is the better.)

Pack any project that has a project reference AND both are using this task to automate versions.

Expected Behavior

Version dependency in packaged NuSpec will have correct version

Actual Behavior
Nuspec file in the generated package has a dependency version of 1.0.0 for all project references.

Additional context
This is the source of the versioning bug reported in Ubiquity.NET.Llvm

This appears to be that the version generation doesn't run when the pack command is calling its own task to retrieve the version information for the referenced projects.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugReported as a bug

    Type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions