Skip to content

Conversation

@ViktorHofer
Copy link
Member

@ViktorHofer ViktorHofer commented Mar 3, 2025

Extracted from #1185
Contributes to dotnet/source-build#1690

The SDK uses the PackageVersion property as an input to NuGet package pruning and conflict resolution.

Having correct inputs passed to conflict resolution is essential to support ProjectReferences in this repository as it handles deciding which asset to compile against (framework vs P2P).

Until now, all projects use the default repository wide version information which is wrong.

Therefore, update the task, template and msbuild generate project entrypoint to emit the PackageVersion property into the project files.

Commit 2 is auto-generated via generate.sh, only with unrelated files reverted. Commit 3 was applied manually.

The SDK uses the PackageVersion property as an input to NuGet package pruning and conflict resolution.

Having correct inputs passed to conflict resolution is essential to support ProjectReferences in this repository as it handles deciding which asset to compile against (framework vs P2P).

Until now, all projects use the default repository wide version information which is wrong.

Therefore, update the task, template and msbuild generate project entrypoint to emit the PackageVersion property into the project files.
Automated change via the generate.sh script (and then filtering out unrelated changes).
@ViktorHofer ViktorHofer requested a review from a team as a code owner March 3, 2025 15:30
@ViktorHofer ViktorHofer merged commit 964c28e into main Mar 3, 2025
4 checks passed
@ViktorHofer ViktorHofer deleted the PackageVersionMetadata branch March 3, 2025 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants