[main] CLI-based tools in eng directory failing to build with error CS0246

[Winniexu01]

Related to dotnet/sdk#48523

https://dev.azure.com/dnceng/internal/_build/results?buildId=2689462&view=logs&j=fa5c2909-0e29-5671-d5eb-16d6c40e0c4a&t=2a0bd486-3f67-5c59-da0c-b84d88848a4b&l=23 (internal Microsoft link)

Scan for binaries building failed with below message:

/mnt/vss/_work/1/s/eng/tools/BinaryToolKit/Program.cs(61,20): error CS0246: The type or namespace name 'Command' could not be found (are you missing a using directive or an assembly reference?) [/mnt/vss/_work/1/s/eng/tools/BinaryToolKit/BinaryToolKit.csproj]
/mnt/vss/_work/1/s/eng/tools/BinaryToolKit/Program.cs(71,42): error CS0246: The type or namespace name 'Command' could not be found (are you missing a using directive or an assembly reference?) [/mnt/vss/_work/1/s/eng/tools/BinaryToolKit/BinaryToolKit.csproj]
/mnt/vss/_work/1/s/eng/tools/BinaryToolKit/Program.cs(12,28): error CS0246: The type or namespace name 'Argument<>' could not be found (are you missing a using directive or an assembly reference?) [/mnt/vss/_work/1/s/eng/tools/BinaryToolKit/BinaryToolKit.csproj]
/mnt/vss/_work/1/s/eng/tools/BinaryToolKit/Program.cs(18,28): error CS0246: The type or namespace name 'Option<>' could not be found (are you missing a using directive or an assembly reference?) [/mnt/vss/_work/1/s/eng/tools/BinaryToolKit/BinaryToolKit.csproj]
/mnt/vss/_work/1/s/eng/tools/BinaryToolKit/Program.cs(25,28): error CS0246: The type or namespace name 'Option<>' could not be found (are you missing a using directive or an assembly reference?) [/mnt/vss/_work/1/s/eng/tools/BinaryToolKit/BinaryToolKit.csproj]
/mnt/vss/_work/1/s/eng/tools/BinaryToolKit/Program.cs(33,28): error CS0246: The type or namespace name 'Option<>' could not be found (are you missing a using directive or an assembly reference?) [/mnt/vss/_work/1/s/eng/tools/BinaryToolKit/BinaryToolKit.csproj]

[mthalman]

@ViktorHofer - Looks like the version of Arcade being used here doesn't yet bring in the new S.CL changes. Do you know the story here?

[mthalman]

This is also failing in the CreateBaselineUpdatePR project:

/mnt/vss/_work/1/s/eng/tools/CreateBaselineUpdatePR/Program.cs(87,20): error CS0246: The type or namespace name 'Command' could not be found (are you missing a using directive or an assembly reference?) [/mnt/vss/_work/1/s/eng/tools/CreateBaselineUpdatePR/CreateBaselineUpdatePR.csproj]

https://dev.azure.com/dnceng/internal/_build/results?buildId=2689642&view=results (internal link)

[ViktorHofer]

The stage2 build in the VMR got fixed today with dotnet/dotnet@f09dba3

Are these components using different dependencies somehow?

[ViktorHofer]

Is there a binlog that I can take a look at?

[mthalman]

These tools are just using Arcade to install the SDK, which is using the version from the global.json.

[mthalman]

No binlog is captured for these tools.

[mthalman]

This is the SDK it's installing: https://ci.dot.net/public/Sdk/10.0.100-preview.4.25216.3/dotnet-sdk-10.0.100-preview.4.25216.3-linux-x64.tar.gz

[ViktorHofer]

dotnet/sdk#48544

[ViktorHofer]

Also filed #5055

[MichaelSimons]

Is this going to require a re-bootstrap to pick up the fix?

[ViktorHofer]

No. The impacted tools (BinaryToolKit (for tagging), CreateBaselineUpdatePR and BuildComparer) use the version that is specified in Versions.props, regardless of the SDK and PSB.

The latest build is already green: https://dev.azure.com/dnceng/internal/_build/results?buildId=2689702&view=results

[MichaelSimons]

My suggestion in #4976 (comment) would have prevented this. We should be using the PSB versions in source-build scenarios. ...But we should still be updating the versions.props appropriately.

[ViktorHofer]

Agreed. It would be great if we could add support for that in source-build scenarios. That said, tools that run inside a source-only context still depend on an accurate version in Versions.props / Directory.Packages.props.

FWIW referencing the tool projects (BuildComparer, CreateBaselineUpdatePR and BinaryToolKit) in tools.proj would've also prevented this.