Closed amis92 closed 6 years ago
To prevent this in the future i'm working on referencing nuget packages that are packed during test instead of referencing projects directly. Brb when I'm done. It also may help to detect what's wrong.
It definitely looks like a ~regression of~ https://github.com/AArnott/Nerdbank.GitVersioning/issues/113
EDIT: strikethrough because it seems this project didn't update the Nerdbank.GitVersioning to 2.1.23+ :D
Good catch.
It's also interesting that my VS hangs when I'm trying to update this package
Created a PR: https://github.com/AArnott/Nerdbank.MSBuildExtension/pull/1 . I hope it gets fixed quickly. When it get's merged we need syncronous update in this repo. It also would be nice if @AArnott could just push it in master when MSBuildExtension gets updated.
I don't see how this is related to https://github.com/AArnott/Nerdbank.MSBuildExtension/pull/1. That project doesn't determine the package versions/dependencies of its consumers like this project.
I can see from the CI build that this issue is already fixed. Probably by #62
@AArnott you're right, I just was searching for possible bad guys in the entire dependency tree :)
Waiting for an updated published nuget.
Published.
Something went wrong with building NuGet packages, because they all require "1.0.0" of the other project dependencies, namely:
dotnet-codegen
requiresCodeGeneration.Roslyn
v1.0.0CodeGeneration.Roslyn
requiresCodeGeneration.Roslyn.Attributes
v1.0.0All packages have package and assembly version set correctly to 0.4.37.
cc @AArnott @Pzixel